From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: nathan@codesourcery.com, gdb@sourceware.org, gdb-patches@sourceware.org
Subject: Re: Bogus change to gdb.base/cursal.exp?
Date: Wed, 02 Aug 2006 21:19:00 -0000 [thread overview]
Message-ID: <200608022117.k72LH4eR004504@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060801225822.GA26808@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 1 Aug 2006 18:58:22 -0400)
> Date: Tue, 1 Aug 2006 18:58:22 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Wed, Aug 02, 2006 at 12:38:18AM +0200, Mark Kettenis wrote:
> > Looking at these error messages, your last change to
> > gdb.base/cursal.exp:
> >
> > 2006-07-24 Nathan Sidwell <nathan@codesourcery.com>
> >
> > * gdb.base/auxv.exp: Skip on non-linux, non-solaris targets.
> > * gdb.base/cursal.exp: Use gdb_file_cmd first, then separate gdb_load.
> >
> > just can't be right. Can you please back the gdb.base/cursal.exp bit out?
>
> I thought Nathan had fixed this on HEAD, but I guess he didn't check in
> the fix. I've taken care of this with the attached patch, from
> gdb-csl-20060226-branch.
> 2006-08-01 Nathan Sidwell <nathan@codesourcery.com>
>
> * gdb.base/cursal.exp: Add "" to gdb_load call.
>
Sorry guys, but this still doesn't work on a native GDB:
Running ../../../../src/gdb/gdb/testsuite/gdb.base/cursal.exp ...
ERROR: couldn't load into /home/kettenis/obj/gdb/gdb/testsuite/../../gdb/gdb (timed out).
So I repeat my request; would you be so kind to back this out until
you've found a solution that doesn't break this test on a native GDB?
Mark
next prev parent reply other threads:[~2006-08-02 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 22:40 Mark Kettenis
2006-08-01 22:58 ` Daniel Jacobowitz
2006-08-02 9:00 ` Nathan Sidwell
2006-08-02 21:19 ` Mark Kettenis [this message]
2006-08-02 22:30 ` 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=200608022117.k72LH4eR004504@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=nathan@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