OK, I've updated by build environment and OpenOCD does not crash anymore. But I still have problems with RTOS support...
If I start OpenOCD and then start GDB via command line, and do following: > file ... > set arm abi APCS // to "solve" the remote g packet problem > target remote ... > info threads I see the threads. I can now quit GDB and start it via Eclipse and I see the threads there. But if I hard-reset everything (quit OpenOCD, shutdown GDB, cycle target's power, ...) and try to go directly to GDB via Eclipse - no threads can be seen (OpenOCD says "No symbols for FreeRTOS" over and over again). I start GDB externally (just connect, nothing more), close it, go back to Eclipse - it works fine... I think that this is some kind of configuration problem, but I really can't tell how previous instance of GDB can affect new instance of GDB other than altering OpenOCD's state... What else? Now bots "-rtos FreeRTOS" and "-rtos auto" work fine, so that's cool (; All above was done with "-rtos FreeRTOS". When I use "-rtos auto" and start GDB in Eclipse there are no errors (No FreeRTOS symbols), but the discovery message (Auto-detected RTOS: FreeRTOS) is seen only after I connect with GDB run in command line - Eclipse with GDB does not trigger such behavior... /; I'm really confused /; 4\/3!! ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
