public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Mitchell <mark@codesourcery.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: 3.2 branch/openserver g++ test results looking bad
Date: Thu, 24 Oct 2002 15:52:00 -0000	[thread overview]
Message-ID: <20021024162133.GA3865@nevyn.them.org> (raw)
In-Reply-To: <20021024160920.GC23898@rjlhome.caldera.com>

On Thu, Oct 24, 2002 at 11:09:20AM -0500, Robert Lipe wrote:
> > Set a breakpoint on default_globalize_label and see where the two
> > calls are coming from.
> 
> Which exposes us to GDB not reading the Dwarf output. :-(
> 	Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.

This is fixed in GDB 5.2.1, if I remember rightly...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2002-10-24 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23 15:58 Robert Lipe
2002-10-24  9:21 ` Mark Mitchell
2002-10-24 15:31   ` Robert Lipe
2002-10-24 15:52     ` Daniel Jacobowitz [this message]
2002-10-24 21:15     ` Robert Lipe

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=20021024162133.GA3865@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).