From: Daniel Jacobowitz <drow@false.org>
To: Nathan Sidwell <nathan@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: gdb.base/break.c change
Date: Tue, 28 Nov 2006 21:53:00 -0000 [thread overview]
Message-ID: <20061128215300.GA1674@nevyn.them.org> (raw)
In-Reply-To: <20061128180945.GA25046@nevyn.them.org>
On Tue, Nov 28, 2006 at 01:09:45PM -0500, Daniel Jacobowitz wrote:
> On Tue, Nov 28, 2006 at 05:55:01PM +0000, Nathan Sidwell wrote:
> > Daniel Jacobowitz wrote:
> > >Hi Nathan,
> > >
> > >Your break.c patch (fixing define.exp in some configuration) broke
> > >break.exp. It's not expecting something between the start of main and
> > >the first breakpoint, I think.
> >
> > oh fiddle sticks. I've committed this after verifying.
>
> Wrong patch attached?
Wrong patch checked in; you added a verbose -log and didn't fix the
test. Bit late there by now, but could you check your working
directory tomorrow? Thanks in advance.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-28 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 17:14 Daniel Jacobowitz
2006-11-28 17:55 ` Nathan Sidwell
2006-11-28 18:10 ` Daniel Jacobowitz
2006-11-28 21:53 ` Daniel Jacobowitz [this message]
2006-11-29 8:03 ` Nathan Sidwell
2006-11-29 14:02 ` 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=20061128215300.GA1674@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@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