From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc] trad-frame change
Date: Wed, 03 Mar 2004 20:20:00 -0000 [thread overview]
Message-ID: <40463E1C.1060502@gnu.org> (raw)
Message-ID: <20040303202000.6vb9F1U2ulzh-lQ4YaNrPSddjHtBjR8d511QFIWtL38@z> (raw)
In-Reply-To: <20040303185319.GA19699@nevyn.them.org>
> There are four kinds of signal frames on MIPS/Linux that we have to
> recognize:
> - o32 sigreturn
> - o32 rt_sigreturn
> - n32 rt_sigreturn
> - n64 rt_sigreturn
>
> They're all basically the same but the offsets differ. Kind could be
> moved out of the cache, I think, since it isn't used after the cache is
> filled. So I could use your new mechanism after all.
So there are really two variants - o32sigreturn and rt_sigreturn (with
constants computed from the architecture vector)?
> What would _really_ be nice would be a way to pass the kind from the
> sniffer (which really just calls PC_IN_SIGTRAMP) to the frame creation
> code... not have to read inferior memory to figure out which it is,
> twice.
I'll think about that, I may need to change the unwinder object anyway.
Just remember that it is the number of unique addresses accessed (0 vs 1
vs 2 ...) and not the number of times each address is accessed that is
going to be important - multiple accesses to a single address can be
handled with a cache.
Andrew
next prev parent reply other threads:[~2004-03-03 20:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Andrew Cagney
2004-03-03 16:43 ` Andrew Cagney
2004-03-03 16:49 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
2004-03-03 18:34 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-03 18:53 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney [this message]
2004-03-03 20:20 ` Andrew Cagney
2004-03-03 20:29 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
2004-03-03 20:41 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-05 14:52 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz
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=40463E1C.1060502@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.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