Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Maxim Grigoriev <maxim@tensilica.com>
To: gdb@sourceware.org, Bob Wilson <bwilson@tensilica.com>,
	  Daniel Jacobowitz <drow@false.org>
Subject: Re: GDB (mis)behavior depends on DWARF DW_TAG_compile_unit data
Date: Thu, 15 Mar 2007 02:03:00 -0000	[thread overview]
Message-ID: <45F8A972.7090406@hq.tensilica.com> (raw)
In-Reply-To: <20070312215821.GA24531@caradoc.them.org>

I found what the problem is. It's strictly Tensilica-compiler-specific.

I suggest we discuss it on the gdb-patch list since I already tried
to provide a patch to fix this issue.

If we end up with understanding that compiler should be fixed then
my GDB patch should be modified to recognize inconsistent DWARF and
issue a warning instead of printing misleading error messages (like it 
does now).

-- Maxim

Daniel Jacobowitz wrote:
> On Mon, Mar 12, 2007 at 02:54:05PM -0700, Maxim Grigoriev wrote:
>   
>> Let me find out what it is and get back to you with my conclusions. It's 
>> still can be
>> important for GDB in terms of better handling bad DWARF data.
>>     
>
> Thanks - I completely agree.  It's not the obvious problem, but
> whatever it is, we should fix it if we can.
>
>   


  reply	other threads:[~2007-03-15  2:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 20:33 Maxim Grigoriev
2007-03-12 20:49 ` Daniel Jacobowitz
2007-03-12 21:06   ` Maxim Grigoriev
2007-03-12 21:23     ` Joel Brobecker
2007-03-12 21:54       ` Maxim Grigoriev
2007-03-12 21:58         ` Daniel Jacobowitz
2007-03-15  2:03           ` Maxim Grigoriev [this message]
2007-03-12 20:57 ` Bob Wilson

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=45F8A972.7090406@hq.tensilica.com \
    --to=maxim@tensilica.com \
    --cc=bwilson@tensilica.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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