![]() If I remove the USB cable (terminate connection to microprocessor), (I thought that might crash the crashed process), I start seeing ~50% available CPU being used (not sure on what), and everything locks up. Nothing kills either cgdb or the process running in it. it is being run on a hypervisor, the debug boot-arg has been set to DBNMI and a non-maskable interrupt (NMI) is triggered (osfmk/i386/mp.cL628/L638) the debug boot-arg has been set to any value (even invalid ones) and a panic occurs (osfmk/kern/debug.cL278/L290). I'm not sure if something gets locked and never unlocked, but cgdb never exits. I'm fairly sure this is because if I kill from halfway through the application, I never release the /dev/ttyUSB device that I'm accessing the microcontroller through. cgdb refuses to ever kill the process - just sits there. Find a bug, or try to exit the still running process using kill inside cgdb.For more help on gdb, read the documentation. To debug the program, you run gdb a.out (or gdb deng) and then type run. Set some breakpoints, etc, do some debugging The binary is called a.out (and you can change the program name to deng by running gcc -g deng.c -o deng) To actually run the program, you have to run.I'm debugging using cgdb on Mac OS X 10.7.3. ![]() I've got a C++ application which connects over a USB serial link to a microprocessor, (similar to an Arduino).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |