From: Michael Elizabeth Chastain <mec@shout.net>
To: ezannoni@redhat.com, kewarken@qnx.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [Patch] fix for PR:1291
Date: Tue, 23 Sep 2003 21:25:00 -0000 [thread overview]
Message-ID: <200309232125.h8NLPf0f031810@duracef.shout.net> (raw)
eza> I wonder if this can be captured in a test case?
Yes, see testsuite/gdb.arch/i386-prologue.exp for a prologue
test case by Mark Kettenis.
The idea is to write explicit assembly code and then check
gdb's behavior on it. That avoids the compiler dependency.
Michael C
next reply other threads:[~2003-09-23 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 21:25 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-16 18:48 kewarken
2003-09-23 21:03 ` Elena Zannoni
2003-09-24 1:20 ` Kris Warkentin
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=200309232125.h8NLPf0f031810@duracef.shout.net \
--to=mec@shout.net \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kewarken@qnx.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