From: Mark Salter <msalter@redhat.com>
To: jlarmour@redhat.com
Cc: john@talisker.demon.co.uk, ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] gdb 'next' problem with i386 HAL
Date: Wed, 05 Sep 2001 09:33:00 -0000 [thread overview]
Message-ID: <200109051633.f85GXuN30119@deneb.localdomain> (raw)
In-Reply-To: <3B964AE0.10557995@redhat.com>
>>>>> Jonathan Larmour writes:
> So you've presumably added something to switch to the interrupt stack. Fair
> enough, but isn't that a separate issue? The SP value stored in the
> HAL_SavedRegisters is still off by 16 no matter what stack you're running
> on. The SP value to report to GDB must still be the value at the time of
> the exception, not the value just after it, no matter what.
I pop those values off the application stack before copying them to the
stub stack frame. The correct SP just comes out of that. I'm not sure
that simply adjusting the SP is sufficient. It may be for 'next' but
inferior function calls may corrupt the area under the SP passed to
GDB.
--Mark
next prev parent reply other threads:[~2001-09-05 9:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 6:42 John Gumb
2001-08-29 6:47 ` Mark Salter
2001-09-05 8:32 ` Jonathan Larmour
2001-09-05 8:44 ` Mark Salter
2001-09-05 8:55 ` Jonathan Larmour
2001-09-05 9:33 ` Mark Salter [this message]
2001-09-05 14:16 ` Jonathan Larmour
2001-09-05 14:59 ` Mark Salter
2001-09-05 15:17 ` Jonathan Larmour
-- strict thread matches above, loose matches on Subject: below --
2001-08-24 7:19 Patrick O'Grady
2001-08-23 2:54 John Gumb
2001-08-22 12:20 Allan Young
2001-08-15 15:08 John Gumb
2001-08-16 6:44 ` Jonathan Larmour
2001-08-17 0:31 ` Boris V. Guzhov
2001-08-17 6:17 ` Jonathan Larmour
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=200109051633.f85GXuN30119@deneb.localdomain \
--to=msalter@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@redhat.com \
--cc=john@talisker.demon.co.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).