Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Chris Demetriou" <cgd@google.com>
To: "Chris Demetriou" <cgd@google.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] fix for rbreak issue w/ "Junk at end of arguments"
Date: Sat, 22 Mar 2008 07:20:00 -0000	[thread overview]
Message-ID: <2e7be40c0803220020h4acff8a1tf02402df6792c481@mail.gmail.com> (raw)
In-Reply-To: <2e7be40c0803220015h500b84fft723d595bfeb9888d@mail.gmail.com>

On Fri, Mar 21, 2008 at 8:32 AM, Daniel Jacobowitz <drow@false.org> wrote:
> Thanks for fixing this.  It's OK, modulo our whitespace conventions
> (space before paren); I fixed that and checked it in.

Ahh, how I've missed the GNU coding conventions.  8-)  Thanks.


> Want write access?
> If so, fill out the sourceware.org form; it's on the front page of the
> web site.

Sure, why not.  It's easier (for you all 8-) than having you apply
patches for me.


> 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.

Yeah.  It seemed likely that this didn't fail in the same way for
everybody -- otherwise I think a lot of people would have screamed by
now, and it would have been fixed sooner.

That's why I coded the test so that it didn't even *attempt* to verify
a breakpoint on the @plt symbol on linux, and that's also why i
verified that the issue existed on two different distro's.

I don't have a system on which it did not fail previously, otherwise i
probably would have investigated a bit further before submitting the
patch.  (Now that you have confirmed that the patch is reasonable, I
don't really want to spend time investigating, of course.  8-)



thanks,

chris


      parent reply	other threads:[~2008-03-22  7:20 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
     [not found]   ` <2e7be40c0803220015h500b84fft723d595bfeb9888d@mail.gmail.com>
2008-03-22  7:20     ` Chris Demetriou [this message]

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=2e7be40c0803220020h4acff8a1tf02402df6792c481@mail.gmail.com \
    --to=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