From: Quality Quorum <qqi@world.std.com>
To: <gdb@sources.redhat.com>
Subject: gdb & arm
Date: Thu, 04 Oct 2001 09:01:00 -0000 [thread overview]
Message-ID: <Pine.SGI.4.30.0110041140360.21435-100000@world.std.com> (raw)
Hi,
I run into annoying problem with arm gdb, it is still there
in gdb-20011002: if set a break point into function, then function
parameters will be printed incorrectly when break point is hit.
It seems that breakpoint is hit before the function prologue is complete,
gdb uses symbol description applicable to the body of the function, and
before function prologue is done symbols simply do not match
their descriptions.
Everything gets back to normal once you reach the first source line
in the function.
It is not terminal problem but quite annoying one.
I am wondering are there any way to fix it. I suppose it should
be trivially simple in case of arm with apcs-32 ?
Can anybody help ?
Thanks,
Aleksey
next reply other threads:[~2001-10-04 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 9:01 Quality Quorum [this message]
2001-10-04 9:13 ` Keith Seitz
2001-10-04 11:32 ` Quality Quorum
2001-10-04 11:37 ` Keith Seitz
2001-10-04 13:31 ` Quality Quorum
2001-10-04 15:00 ` Keith Seitz
2001-10-04 16:08 ` Quality Quorum
2001-10-05 9:37 ` Fernando Nasser
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=Pine.SGI.4.30.0110041140360.21435-100000@world.std.com \
--to=qqi@world.std.com \
--cc=gdb@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