Jason Wessel <[email protected]> writes:
> If by not the same, do you mean that it jumps all over the place in the
> debugger? If so, that is to be expected if you are using -O2 optimized
> code.
I wonder if this is related to my report of "next == step", where you
can't single-step across a function, but instead you can only step into
every function/call.. and 'fin' doesn't work.
To someone used to gdb, when you say "next" and don't see the next line
of your current function it can be very confusing. This is made worse
when the function you want to step across is "printk". It takes FOREVER
to get out of that.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[email protected] PGP key available
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
