User forums > Embedded development
CodeBlocks and Codesourcery GDB
oBFusCATed:
Does you executable captures Ctrl+C/SIGINT and after that resending it to the real GDB?
If not can you try to implement it and report if this is working?
Keep in mind that you have to have a console allocated in order for this to work.
Lost_Byte:
--- Quote from: oBFusCATed on March 19, 2012, 11:12:19 am ---Does you executable captures Ctrl+C/SIGINT and after that resending it to the real GDB?
--- End quote ---
How should it looks?
After SIGINT to debugging exec in C::B "Debugger(debug)" log view contains following (my comments under ///):
/// run exec to while(1) loop...
> continue
/// send CTRL+C
Cannot access memory at address 0x0
Program received signal SIGINT, Interrupt.
0x402b9d58 in ?? ()
>>>>>>cb_gdb:
/// some commands by debugee to obtain current exec state
oBFusCATed:
I don't understand your question. Can you clarify it a bit?
Lost_Byte:
--- Quote from: oBFusCATed on March 19, 2012, 11:12:19 am ---Does you executable captures Ctrl+C/SIGINT and after that resending it to the real GDB?
--- End quote ---
What did you mean under "resending"?
How should it looks for me during debugging session under C::B?
Lost_Byte:
--- Quote from: oBFusCATed on March 19, 2012, 11:12:19 am ---Does you executable captures Ctrl+C/SIGINT and after that resending it to the real GDB?
--- End quote ---
Oh.. It seems, I got it... "Executable"- means, my "gdb-cb-bridge" sketch? Is it?
If it's so - answer, no, "gdb-cb-bridge" does not handle SIGINT... I'll try to implement.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version