From: Daniel Jacobowitz <drow@mvista.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: [testsuite & dwarf2] How to handle store.exp failure on AMD64?
Date: Thu, 07 Aug 2003 13:50:00 -0000 [thread overview]
Message-ID: <20030807135035.GA28000@nevyn.them.org> (raw)
In-Reply-To: <3F3212B7.8060003@suse.cz>
On Thu, Aug 07, 2003 at 10:49:59AM +0200, Michal Ludvig wrote:
> 4) let GDB pretend that all registers have the same value unless said
> otherwise later in the .debug_frame and convince GCC to put a note when
> their value is overwritten.
>
> Opinions?
See the archives of this list, from about a month ago. I discussed
this with Richard but never got around to writing a patch.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-07 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 8:49 Michal Ludvig
2003-08-07 13:50 ` Daniel Jacobowitz [this message]
2003-08-07 14:58 ` Andrew Cagney
2003-08-07 15:02 ` Daniel Jacobowitz
2003-08-07 15:53 ` Andrew Cagney
2003-08-07 21:40 ` Michal Ludvig
2003-08-13 3:54 ` Andrew Cagney
2003-08-13 4:54 ` Richard Henderson
2003-08-13 14:39 ` Andrew Cagney
2003-08-13 16:50 ` Richard Henderson
2003-08-13 18:23 ` Andrew Cagney
2003-08-13 23:35 ` Richard Henderson
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=20030807135035.GA28000@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mludvig@suse.cz \
/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