From: "Eli Zaretskii" <eliz@gnu.org>
To: mec.gnu@mindspring.com
Cc: kettenis@chello.nl, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add test for PR backtrace/1718
Date: Sat, 24 Jul 2004 07:58:00 -0000 [thread overview]
Message-ID: <8011-Sat24Jul2004105628+0300-eliz@gnu.org> (raw)
In-Reply-To: <41016FDB.nailGNO1TVAI5@mindspring.com> (mec.gnu@mindspring.com)
> Date: Fri, 23 Jul 2004 16:06:51 -0400
> From: mec.gnu@mindspring.com
>
> As soon as I saw:
>
> pushl %ebp
> movl $0x11111111, %eax
> movl %esp, %ebp
>
> ... I knew that Mark would nail it!
Bother: are you saying that Mark posted a patch to fix the problem?
Because if he did, I somehow missed that.
prev parent reply other threads:[~2004-07-24 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 13:08 Mark Kettenis
2004-07-23 20:06 ` mec.gnu
2004-07-24 7:58 ` Eli Zaretskii [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=8011-Sat24Jul2004105628+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=mec.gnu@mindspring.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