I'm trying to set a breakpoint for the debugger to stop on. I'm using the breakpoint function in rtl_debug.h. It seems to stop but I can't access the module from GDB (actually DDD) by using the command 'target remote /dev/rtf10'. GDB hangs as it searches and when I kill GDB, it complains that it cannot connect to the remote host.
I know that the debugger is working because it will stop my module on a line that has an error in it. I can call the same target command from within GDB this time and it works. I can connect to the code and step through it. But I want to stop before I read that error line so I can see what's happening before it. Does the type of signal sent to a module affect GDB's ability to access it? I think my module gets sent SIGHUP (probably by rtl_debug) when it crashes. I've also tried executing really bad code to try and cause an error but rtlinux seems very happy about accessing portions of memory that I don't own and even dividing by zero (5/0 = 0 in rtlinux)! Any ideas? Tim -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/
