Re: [Kgdb-bugreport] Problems while debugging Native IPSec using KGDB

[Anupam C. <anu...@gm...>]

Hi,

Thanks both of you for your suggestions!

I wanted to send this reply so that others can use this info tomorrow
for their debugging!!

As Jason had suggested, I added -O0 as compiling options in the
relevant makefiles. In brief:

1. The root makefile had CFLAGS -O2 option set. I changed that to O0.
2. I modified the makefiles in net/ and net/ipv4/ and added the O0
options. But while make, I got error in xfrm4_state. So I had to
specifically add O2 for xfrm_state.o (As Jason had mentioned).
3. Atleast the debugging is much better now!

Derek, as you mentioned, I am trying to do next whereas step is
actually getting executed! Finish causes an error saying break point
could not be set. I do not want to enter functions, so any suggestions
for that!!

BRegards,

Anupam.

On Mon, May 11, 2009 at 9:18 PM, Derek Atkins <wa...@mi...> wrote:
> Jason Wessel <jas...@wi...> 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
>       warlord@MIT.EDU                        PGP key available
>