On Saturday 27 August 2005 03:49, Allan Graves wrote:
> I thought i had this thread trace thing several times, but I couldn't
> get gdb to stop on breakpoints, its like it was ignoring them.... it
> thought everything was in thread_info.h. And it listed the right code,
> and i could do like b 26, and it would set a breakpoint for line 26 of
> the correct function with the correct filename, and then just ignore it.
If you break on an exact line, then it may still be that you found a "no-op"
line (which means for instance comments, but GCC optimization may make you
However, apart from that, I've seen that happen too when trying to do things
like break panic. I think I've never seen it working. I don't know if Jeff
has it working (he's been staying with gdb 5.x to avoid lots of problems in
However, please first disable TT mode and checks if that changes anything...
> (gdb) info b
> Num Type Disp Enb Address What
> 1 breakpoint keep y 0x0806f607 in panic at kernel/panic.c:74
> 2 breakpoint keep y 0x0805c254 in switch_to_skas at
> 3 breakpoint keep y 0x081e5ac5 in schedule at thread_info.h:50
> 4 breakpoint keep y 0x081e6037 in schedule at kernel/sched.c:2747
> Any suggestions?
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> User-mode-linux-devel mailing list
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB