From: Andrew Cagney <ac131313@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Convert ARM to generic dummy frames
Date: Sun, 05 May 2002 20:24:00 -0000 [thread overview]
Message-ID: <3CD5F789.5040504@cygnus.com> (raw)
In-Reply-To: <3CD3E422.3040700@cygnus.com>
> I've tested it against the simulator for arm{,be}{,thumb}.
> Look ok?
>
> Just got pointed out (in private) that I didn't use the right -mthumb option :-( Back to testing.
Testing xscale-elf{,-mbig-endian}{,-mthumb} I get two differences:
gdb.base/break.exp: backtrace while in called function
This starts passing for -mthumb!
gdb.c++/virtfunc.exp: print pEe->D::vg
This, and a few others disappear for -mthumb. What is really happening
is that the earlier test:
print pDe->vg()
FAIL: gdb.c++/virtfunc.exp: print pDe->vg() (timeout)
has caused the target to go for a walk (occures with old and new).
Since the stack for the two test cases are slightly different, the exact
walk (I think) varies leading to the differences. The modified target
eventually aborts when it runs out of memory.
Thoughts?
Andrew
next prev parent reply other threads:[~2002-05-06 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 6:17 Andrew Cagney
2002-05-04 6:37 ` Andrew Cagney
2002-05-05 20:24 ` Andrew Cagney [this message]
2002-05-07 18:02 ` Andrew Cagney
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=3CD5F789.5040504@cygnus.com \
--to=ac131313@cygnus.com \
--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