From: Andrew STUBBS <andrew.stubbs@st.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [SH][PATCH] Disable ABI frame sniffer
Date: Fri, 11 Nov 2005 20:09:00 -0000 [thread overview]
Message-ID: <4374863D.60601@st.com> (raw)
In-Reply-To: <20051110231336.GB3195@nevyn.them.org>
Hi Daniel,
Daniel Jacobowitz wrote:
> There are assembly routines in newlib too, you know. I didn't say
> anything about glibc. You may encounter linker generated branch
> trampolines in some cases, too.
I know you didn't say anything about glibc. I was just citing that as an
example of a complex library.
Newlib does have assembly routines, but very few, on SH anyway. The only
ones I know of off hand are memset and friends. There's the crt stuff,
of course, but you have to go 'pastmain' to find that.
> In case you missed my sarcasm here, I was responding to "dependent on
> the values in registers and memory". Of course it is!
I didn't miss it as such, but seriously, most of what GDB does doesn't
involve following (possibly phantom) trails of pointers through target
memory. This about the least certain data that GDB presents, simply
because the uncertainties mount up.
> See Mark's reply for more on this. Had you said what your problem
> really was, we could have saved a couple of back-and-forth exchanges;
> I'm extremely familiar with the problem of finding clean ways to
> terminate the backtrace.
OK, I'm listening. If we can get it so that both the 0xdeadbeef frames
(one which comes from the dwarf unwinder - see my posting yesterday) are
ignored then that would be a bonus.
>>BTW, were you (and others) waiting for them to do something about the SH
>>specific patches I have been sending? I ask because I have had no
>>response on a few.
>
>
> I review patches as fast as I am able. I am more likely to review
> patches to code I know something about, which does not include the SH
> backend.
>
I can understand that. I'm sure you have your own real work to be
getting on with too. However, I have a selection of SH specific patches,
submitted and queued, so this situation worries me a little. About half
of sh-tdep.c is a total mystery to me - mostly the bits that have never
caused me any trouble. My patches to that area are all quite simple, so
it probably won't be too bad.
Thanks for all your time
Andrew Stubbs
next prev parent reply other threads:[~2005-11-11 11:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 18:08 Andrew STUBBS
2005-11-10 0:17 ` Andreas Schwab
2005-11-10 3:30 ` Daniel Jacobowitz
2005-11-10 12:27 ` Andrew STUBBS
2005-11-10 14:24 ` Daniel Jacobowitz
2005-11-10 4:27 ` Daniel Jacobowitz
2005-11-10 13:36 ` Andrew STUBBS
2005-11-10 14:34 ` Daniel Jacobowitz
2005-11-10 23:09 ` Andrew STUBBS
2005-11-10 23:13 ` Andrew STUBBS
2005-11-11 0:10 ` Mark Kettenis
2005-11-11 10:31 ` Daniel Jacobowitz
2005-11-11 18:21 ` Andrew STUBBS
2005-11-11 10:35 ` Daniel Jacobowitz
2005-11-11 20:09 ` Andrew STUBBS [this message]
2005-11-13 18:57 ` Daniel Jacobowitz
2005-11-13 23:58 ` Jim Blandy
2005-11-23 19:52 ` Andrew STUBBS
2005-11-24 22:48 ` Andrew STUBBS
2005-11-24 23:42 ` Mark Kettenis
2005-11-10 11:11 ` Eli Zaretskii
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=4374863D.60601@st.com \
--to=andrew.stubbs@st.com \
--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