From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] selftest.exp: bump up initial line count
Date: Sat, 28 Jun 2003 16:37:00 -0000 [thread overview]
Message-ID: <20030628163728.GC9716@nevyn.them.org> (raw)
In-Reply-To: <200306230400.h5N40JUN013198@duracef.shout.net>
On Mon, Jun 23, 2003 at 12:00:19AM -0400, Michael Elizabeth Chastain wrote:
> drow> Could you try this more comprehensive patch?
>
> My testbed says it's okay on all configurations. I think it looks gross
> but it's okay with me considering where we are in the release cycle.
>
> (I have a big Analysis.txt file in progress. It had nine "To Be
> Investigated" left at lunchtime, and I still have five of them left and
> I'm falling asleep.)
>
> Let's throw it on the main line and if it looks all nice after my next
> spin. If it does, then it can go on the release branch.
>
> Michael C
>
> 2003-06-22 Michael Chastain <mec@shout.net>
> Daniel Jacobowitz <drow@mvista.com>
>
> * gdb.base/selftest.exp (do_steps_and_nexts): Increase maximum
> initial line count of 'captured_main' from 26 to 32.
> (test_with_self): Allow xmalloc call to be interleaved with the
> preceding two lines.
Better late than never, I've checked this in to mainline. I'll queue
it for the branch, pending test results or at least no reports of a
problem.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-28 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 4:04 Michael Elizabeth Chastain
2003-06-28 16:37 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-29 16:33 Michael Elizabeth Chastain
2003-06-29 17:37 ` Daniel Jacobowitz
2003-06-23 3:06 Michael Elizabeth Chastain
2003-06-23 3:52 ` 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=20030628163728.GC9716@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