From: "Terry Guo" <terry.guo@arm.com>
To: "'Yao Qi'" <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>, <pedro@codesourcery.com>
Subject: RE: [PATCH] Fix that different function breakpoints are set at same pc address (PR gdb/12703)
Date: Wed, 29 Jun 2011 07:00:00 -0000 [thread overview]
Message-ID: <000501cc362a$2e7f9020$8b7eb060$@guo@arm.com> (raw)
In-Reply-To: <4E0AB9B3.8060104@codesourcery.com>
Hi,
Here is my case. As for stack backtrace, I wonder whether it works for the function that only contains one single instruction and function that doesn't even has a valid prologue. I also saw that current prologue analyzer cannot handle all cases, so I try to avoid this in a more general way.
unsigned long _etext;
unsigned long _data;
unsigned long _edata;
register unsigned long guard asm("r5");
void bar (void);
void test (void) __attribute__((naked));
void
foo (void)
{
while(1)
{
}
} /* End of function foo. */
void
test (void)
{
guard = 10;
}
void
bar (void)
{
unsigned long *pulSrc, *pulDest;
pulSrc = &_etext;
for (pulDest = &_data; pulDest < &_edata;)
{
*pulDest++ = *pulSrc++;
}
if (*pulSrc > guard)
guard = 0;
else
guard = 1;
}
void
main (int argc, char **argv)
{
test ();
}
next prev parent reply other threads:[~2011-06-29 7:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 11:26 Terry Guo
2011-06-29 1:26 ` Terry Guo
2011-06-29 5:36 ` Yao Qi
2011-06-29 7:00 ` Terry Guo [this message]
2011-06-29 8:00 ` Yao Qi
2011-06-29 8:49 ` Terry Guo
[not found] ` <45520D6299C11E4588128526465332BB0D0C8B1246@SAROVARA.Asiapac.Arm.com>
2011-06-29 10:00 ` Yao Qi
2011-06-29 10:17 ` Terry Guo
2011-07-01 8:59 ` Richard Earnshaw
2011-07-01 9:47 ` Pedro Alves
2011-07-13 13:21 ` Terry Guo
-- strict thread matches above, loose matches on Subject: below --
2011-06-24 2:31 Terry Guo
2011-06-24 3:55 ` Yao Qi
2011-06-24 8:59 ` Pedro Alves
2011-06-24 10:39 ` Yao Qi
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='000501cc362a$2e7f9020$8b7eb060$@guo@arm.com' \
--to=terry.guo@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=yao@codesourcery.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