Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: vapier@gentoo.org
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: workaround sparc memcpy fortify error
Date: Wed, 21 Apr 2010 19:56:00 -0000	[thread overview]
Message-ID: <201004211955.o3LJtV69021551@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <201004211540.44433.vapier@gentoo.org> (message from Mike 	Frysinger on Wed, 21 Apr 2010 15:40:43 -0400)

> From: Mike Frysinger <vapier@gentoo.org>
> Date: Wed, 21 Apr 2010 15:40:43 -0400
> 
> On Wednesday 21 April 2010 12:08:54 Mark Kettenis wrote:
> > > > It was a ping for
> > > > http://permalink.gmane.org/gmane.comp.gdb.patches/56350
> > >=20
> > > Aha - Mark Kettenis seemed to be OK with this, since he's the one
> > > who suggested it. Mark, is this patch still OK?
> >=20
> > Hmm, can we keep the existing gdb_assert() and just add the len <=3D 8
> > one?  With that change, this is fine with me.
> 
> fine by me.  i can also add a comment about the gcc PR if people want.

Nah, I don't think that's really necessary in this case.


  reply	other threads:[~2010-04-21 19:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  2:09 [PATCH] gdb: fix " Mike Frysinger
2010-03-19  7:45 ` Eli Zaretskii
2010-03-19  8:18   ` Hui Zhu
2010-03-19  8:42     ` Andreas Schwab
2010-03-19 17:10     ` Mike Frysinger
2010-03-19  9:26 ` Mark Kettenis
2010-03-19 17:09   ` Mike Frysinger
2010-03-19 20:11 ` [PATCH] gdb: workaround " Mike Frysinger
2010-04-19 18:59   ` Mike Frysinger
2010-04-21 15:30     ` Joel Brobecker
2010-04-21 15:38       ` Tom Tromey
2010-04-21 16:01         ` Joel Brobecker
2010-04-21 16:10           ` Mark Kettenis
2010-04-21 19:40             ` Mike Frysinger
2010-04-21 19:56               ` Mark Kettenis [this message]
2010-04-21 20:12                 ` Mike Frysinger

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=201004211955.o3LJtV69021551@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.org \
    /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