From: Richard Henderson <rth@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Michal Ludvig <mludvig@suse.cz>,
Daniel Jacobowitz <drow@mvista.com>, gdb <gdb@sources.redhat.com>
Subject: Re: [testsuite & dwarf2] How to handle store.exp failure on AMD64?
Date: Wed, 13 Aug 2003 23:35:00 -0000 [thread overview]
Message-ID: <20030813233542.GA26172@redhat.com> (raw)
In-Reply-To: <3F3A8203.5060102@redhat.com>
> >Moreover, the algorithm I suggested that you use -- assume saved --
> >is also completely independant of the ABI, so its' not like GDB
> >needs to hard code ABI specific information either.
>
> It doesn't work in general.
> On a register window machine, it could use a fairly complex starting
> state vis:
> globals: same
> locals: where saved on stack
> input: undefined
> output: in input
> (register windows give me a headache so don't assume this one is correct :-)
This has to be handled with the same magic that handles register windows
in the first place. I.e. DW_CFA_GNU_window_save. Dwarf2 doesn't handle
windows itself at all.
You could also do it with explicit dw2 operations, but that's no different
than a non-windowed system than starts with all DW_CFA_same_value and
adds DW_CFA_undefined, DW_CFA_register and DW_CFA_offset notes as needed.
> [perhaphs I should have cross posted this with dwarf2 :-)]
Probably.
r~
prev parent reply other threads:[~2003-08-13 23:35 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
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 [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=20030813233542.GA26172@redhat.com \
--to=rth@redhat.com \
--cc=ac131313@redhat.com \
--cc=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