W dniu 2012-10-16 17:53, Jonathan Dumaresq pisze: > Do you have to add something to the startup script ?
You mean the assembly startup of the MCU or the configs for OpenOCD? In both cases they don't need any changes for RTOS-aware debugging in OpenOCD. You just need to add this command: -c "<your-target-name> configure -rtos auto" > If I use verbose mode of GDB it's works. If I removed it, I could not get > the debug working at all. That's the problem - it sometimes starts working out of nowhere, then stops working for no reason and you're never sure what triggered the behavior... You have to remember that some bits in OpenOCD about this RTOS-awareness seem to be "sticky" - if you get this to work one time, you can change many things in GDB and it will still work - as long as you don't restart OpenOCD - which is when it will stop working [; 4\/3!! ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
