From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix gdb/277 by separating types
Date: Sun, 12 May 2002 19:38:00 -0000 [thread overview]
Message-ID: <20020513023817.GA20252@nevyn.them.org> (raw)
In-Reply-To: <200205130219.g4D2Jch16628@duracef.shout.net>
On Sun, May 12, 2002 at 09:19:38PM -0500, Michael Elizabeth Chastain wrote:
> Mr. Test-Bed choked on this pair of patches. He died early in the
> first configuration tested, in gdb.base/maint.exp.
>
> There's a tarball at
>
> ftp://ftp.shout.net/pub/users/mec/gdb/20020510-drow-test.tar.gz
>
> That includes gdb.log, the gdb executable, and the core file in it.
This is quite odd. The same thing does not happen here, in the roughly
same configuration (gcc 2.95.3+patches instead of 2.95.2). There's a
failure in maint print type, which I expected but forgot to mention (I
changed the debugging output; I'll submit a testsuite fix separately).
I can't even reproduce it with your binary, in my test harness, running
maint.exp!
Does your testbed build in a clean object directory? If not, it's
possible that I missed yet another dependency on gdbtypes.h, but that
seems unlikely from your binary's debug info.
I need a helping hand here.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-13 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 19:19 Michael Elizabeth Chastain
2002-05-12 19:38 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-12 20:13 Michael Elizabeth Chastain
2002-05-12 20:10 Michael Elizabeth Chastain
2002-05-12 20:16 ` Daniel Jacobowitz
2002-05-12 17:53 Daniel Jacobowitz
2002-05-12 22:22 ` Eli Zaretskii
2002-05-13 6:30 ` Andrew Cagney
2002-05-13 6:41 ` Daniel Jacobowitz
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=20020513023817.GA20252@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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