From: sumanth <sumanth.gundapneni@redpinesignals.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>, gdb@sourceware.org
Subject: Re: gcc - gdb compatibility issue
Date: Mon, 27 Apr 2009 13:19:00 -0000 [thread overview]
Message-ID: <49F554B7.400@redpinesignals.com> (raw)
In-Reply-To: <20090427064225.GN32765@adacore.com>
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.
>
>
next prev parent reply other threads:[~2009-04-27 6:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 6:03 sumanth
2009-04-27 6:30 ` Paul Pluzhnikov
2009-04-27 6:32 ` Joel Brobecker
2009-04-27 6:42 ` sumanth
2009-04-27 6:55 ` Joel Brobecker
2009-04-27 13:19 ` sumanth [this message]
2009-04-28 4:41 ` Eli Zaretskii
2009-04-28 6:22 ` sumanth
2009-04-27 6:36 ` sumanth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49F554B7.400@redpinesignals.com \
--to=sumanth.gundapneni@redpinesignals.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox