From: Daniel Jacobowitz <drow@false.org>
To: Chris Demetriou <cgd@google.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] fix for rbreak issue w/ "Junk at end of arguments"
Date: Fri, 21 Mar 2008 15:32:00 -0000 [thread overview]
Message-ID: <20080321153206.GI25307@caradoc.them.org> (raw)
In-Reply-To: <2e7be40c0803150118x58bf76c7r4bf67fc61d07c26a@mail.gmail.com>
On Sat, Mar 15, 2008 at 01:18:09AM -0700, Chris Demetriou wrote:
> If this patch is acceptable, please apply it. (I don't have write access.)
Thanks for fixing this. It's OK, modulo our whitespace conventions
(space before paren); I fixed that and checked it in. Want write access?
If so, fill out the sourceware.org form; it's on the front page of the
web site.
Oddly the test doesn't fail for me even though I've got an
__libc_start_main@plt. It's not setting a breakpoint at the
PLT entry... boo, it thinks that comes from a startfile. Another day.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-21 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 8:18 Chris Demetriou
2008-03-21 15:32 ` Daniel Jacobowitz [this message]
[not found] ` <2e7be40c0803220015h500b84fft723d595bfeb9888d@mail.gmail.com>
2008-03-22 7:20 ` Chris Demetriou
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=20080321153206.GI25307@caradoc.them.org \
--to=drow@false.org \
--cc=cgd@google.com \
--cc=gdb-patches@sources.redhat.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