gcc - gdb compatibility issue

gcc - gdb compatibility issue

[sumanth]

Hi,
I am using gcc-4.3.3 and gdb 5.3 version.
I have problems in  debugging my  binaries (a.out)  concerned to local 
variable's address location.
Is there any gcc-gdb compatibility issue here. If so how can I generate 
the correct debugging information and use it.

Thanks in advance,
Sumanth

Re: gcc - gdb compatibility issue

[Paul Pluzhnikov]

On Sun, Apr 26, 2009 at 10:17 PM, sumanth
<sumanth.gundapneni@redpinesignals.com> wrote:

> I am using gcc-4.3.3 and gdb 5.3 version.

That's a rather new GCC and rather old GDB.

> I have problems in  debugging my  binaries (a.out)  concerned to local
> variable's address location.

What kind of problems?
Did you compile with -O, -O2, or -O3?
Debugging optimized code is always problematic: the compiler may not
have assigned address for a local variable at all.

> Is there any gcc-gdb compatibility issue here. If so how can I generate the
> correct debugging information and use it.

Start by compiling with '-g -O0'.
If that doesn't work, try current GDB built from CVS Head.
If that still doesn't work, show us your compile line, and output from
'gcc --version'.

Cheers,
-- 
Paul Pluzhnikov

Re: gcc - gdb compatibility issue

[Joel Brobecker]

> > I am using gcc-4.3.3 and gdb 5.3 version.
> 
> That's a rather new GCC and rather old GDB.

One of the major problems of debugging GCC 4.3 code with such an old
GDB is that GDB 5.3 doesn't handle location lists (assuming that
the debugging info is DWARF). That may be your problem.

Paul provided a lot of very good advice.  If that doesn't work, you
might want to try the current CVS HEAD or our latest release, which
is 6.8. I'm seeing a lot of hard work being done by several contributors
towards 7.0 as well which hopefully we'll release before June this year.

-- 
Joel

Re: gcc - gdb compatibility issue

[sumanth]

Joel ... Is there a way that i can avoid location lists generated by my 
compiler
and i am using DWARF 2

Thanks to joel and paul
sumanth
Joel Brobecker wrote:
>>> I am using gcc-4.3.3 and gdb 5.3 version.
>>>       
>> That's a rather new GCC and rather old GDB.
>>     
>
> One of the major problems of debugging GCC 4.3 code with such an old
> GDB is that GDB 5.3 doesn't handle location lists (assuming that
> the debugging info is DWARF). That may be your problem.
>
> Paul provided a lot of very good advice.  If that doesn't work, you
> might want to try the current CVS HEAD or our latest release, which
> is 6.8. I'm seeing a lot of hard work being done by several contributors
> towards 7.0 as well which hopefully we'll release before June this year.
>
>   

Re: gcc - gdb compatibility issue

[Joel Brobecker]

> Joel ... Is there a way that i can avoid location lists generated by
> my  compiler and i am using DWARF 2

Not as far as I know. When we discovered that GDB 5.3 wasn't handling
them very well (if at all, actually, I can't remember the symptoms
anymore), we found that the fastest change until we could switch
to a more recent debugger was to hack the compiler to avoid their
generation. Olivier Hainque made the change, it was relatively
localized.

I suspect upgrading the debugger is going to be a lot easier than
hacking the compiler.  That being said, location lists are not
necessarily the actual cause of your specific issue. It would be
hard to tell without debugging the debugger itself.

-- 
Joel

Re: gcc - gdb compatibility issue

[sumanth]

Joel , if you don't mind
can you brief me on this
"

I suspect upgrading the debugger is going to be a lot easier than
hacking the compiler.  That being said, location lists are not
necessarily the actual cause of your specific issue. It would be
hard to tell without debugging the debugger itself.

"

Thanks in advance ,
Sumanth G
Joel Brobecker wrote:
>> Joel ... Is there a way that i can avoid location lists generated by
>> my  compiler and i am using DWARF 2
>>     
>
> Not as far as I know. When we discovered that GDB 5.3 wasn't handling
> them very well (if at all, actually, I can't remember the symptoms
> anymore), we found that the fastest change until we could switch
> to a more recent debugger was to hack the compiler to avoid their
> generation. Olivier Hainque made the change, it was relatively
> localized.
>
> I suspect upgrading the debugger is going to be a lot easier than
> hacking the compiler.  That being said, location lists are not
> necessarily the actual cause of your specific issue. It would be
> hard to tell without debugging the debugger itself.
>
>   

Re: gcc - gdb compatibility issue

[Eli Zaretskii]

> Date: Sun, 26 Apr 2009 23:42:25 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Paul Pluzhnikov <ppluzhnikov@google.com>, gdb@sourceware.org
> 
> I suspect upgrading the debugger is going to be a lot easier than
> hacking the compiler.

Alternatively, the OP could try compiling with -gstabs+ instead of
just -g.

Re: gcc - gdb compatibility issue

[sumanth]

Eli Zaretskii wrote:
>> Date: Sun, 26 Apr 2009 23:42:25 -0700
>> From: Joel Brobecker <brobecker@adacore.com>
>> Cc: Paul Pluzhnikov <ppluzhnikov@google.com>, gdb@sourceware.org
>>
>> I suspect upgrading the debugger is going to be a lot easier than
>> hacking the compiler.
>>     
>
> Alternatively, the OP could try compiling with -gstabs+ instead of
> just -g.
>
>
>   
my target system won't support stabs debugging format

Re: gcc - gdb compatibility issue

[sumanth]

hi,
 I tried compiling with '-g -O0' option, result is same.
 Since I am not using a well known architecture , i need to port gdb to 
my architecture.
 gcc --version gives gcc (GCC) 4.1.1 20061011 (Red Hat 4.1.1-30).

 The problem here is ,it is generating local variables address but not 
in the current frame. But when I compile
 with '-g -O0 -fvar-tracking ' I got partial correct information .
 Let me explain with an example :
 int main()
{
volatile int a, b , c;
a =10;
b =20;
c =add(a,b);
return 0;
}

int add(int x, int y)
{
return x+y;
}

With '-g -O0' all the local variable's address i.e a,b,c generated is wrong.
with '-g -O0 -fvar-tracking ' a,b 's address is generated correct. c 
variable's address is wrong.
I am confident that there is no error from compiler side . So, I am 
asking for any compatibility issue regarding gcc-gdb versions.

sumanth


  
Paul Pluzhnikov wrote:
> On Sun, Apr 26, 2009 at 10:17 PM, sumanth
> <sumanth.gundapneni@redpinesignals.com> wrote:
>
>   
>> I am using gcc-4.3.3 and gdb 5.3 version.
>>     
>
> That's a rather new GCC and rather old GDB.
>
>   
>> I have problems in  debugging my  binaries (a.out)  concerned to local
>> variable's address location.
>>     
>
> What kind of problems?
> Did you compile with -O, -O2, or -O3?
> Debugging optimized code is always problematic: the compiler may not
> have assigned address for a local variable at all.
>
>   
>> Is there any gcc-gdb compatibility issue here. If so how can I generate the
>> correct debugging information and use it.
>>     
>
> Start by compiling with '-g -O0'.
> If that doesn't work, try current GDB built from CVS Head.
> If that still doesn't work, show us your compile line, and output from
> 'gcc --version'.
>
> Cheers,
>