I've found some characteristics of a rtl_debug/gdb problem, and a crude
workaround.
Once in a while, my rtl periodic thread breakpoint doesn't happen
properly: The debugger _does_ break at the proper line of code, and I
_can_ attach and single step in gdb/ddd, but I can't view the true
values of my variables - I get strange, wrong values. When this
happens, it always seems to coincide with the phenomenon that the
following message:
"rtl_debug: exception 0x3 in mocon_loader (EIP=0xd08b80eb), thread id
0xc5878000; (re)start GDB to debug"
DOES NOT appear in dmesg, as it should when the breakpoint was hit.
Additionally, during this faulty session, when "target remote
/dev/rtf10" was executed at the gdb prompt, we got:
"warning: shared library handler failed to enable breakpoint"
The crude workaround is to remove my own module, and reload the RTL
modules (/etc/rc.d/init.d/rtlinux/ stop ... start)
Then, usually, I can get a proper breakpoint (with no missing rtl_debug
message and no gdb warning) and I can view the correct value of my
variables, etc.
Can anyone comment on what the two warnings above mean ?
my system :
gcc 2.95.3
kernel 2.4.18
RTL 3.1
gdb 5.1.90
RedHat 7.3
(I understand that people have gotten things working better with older
releases of gdb.)
_______________________________________________
Rtl mailing list
[EMAIL PROTECTED]
http://www2.fsmlabs.com/mailman/listinfo.cgi/rtl
