From: Andreas Jaeger <aj@suse.de>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix possible buffer overflow bug in x86_64-tdep.c
Date: Mon, 14 Jul 2003 08:55:00 -0000 [thread overview]
Message-ID: <hollv1v66t.fsf@byrd.suse.de> (raw)
In-Reply-To: <200307131631.h6DGVkvI098450@elgar.kettenis.dyndns.org> (Mark Kettenis's message of "Sun, 13 Jul 2003 18:31:46 +0200 (CEST)")
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
Mark Kettenis <kettenis@chello.nl> writes:
> The attached fixes a possible buffer overflow in
> x86_64_store_return_value().
>
> (Andreas, this was the bug I mentioned to you yesterday).
Looks fine to me - thanks!
> Andreas forgot to check in his origional patch on the 6.0 release
> branch. I'll do so shortly with this fix included.
thanks a lot!
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2003-07-14 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 16:32 Mark Kettenis
2003-07-14 8:55 ` Andreas Jaeger [this message]
2003-07-14 19:25 ` Mark Kettenis
2003-07-13 22:09 Mark Kettenis
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=hollv1v66t.fsf@byrd.suse.de \
--to=aj@suse.de \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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