From: Nick Roberts <nickrob@snap.net.nz>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Cameron Stone <camerons@cse.unsw.edu.au>, gdb@sourceware.org
Subject: Re: expanding backtrace
Date: Thu, 29 Jun 2006 03:48:00 -0000 [thread overview]
Message-ID: <17569.47799.735812.759914@kahikatea.snap.net.nz> (raw)
In-Reply-To: <44A14571.20003@st.com>
> You could write something like
>
> while $pc != 0
I don't think that works.
> or
>
> while $sp <= $topofmem
>
> It depends how your backtraces end.
If you mean:
(gdb) start
...
(gdb) set $topofmem=$sp
and use "$sp < $topofmem" for the loop condition, then that looks like a good
idea.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2006-06-27 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 3:05 Cameron Stone
2006-06-28 14:02 ` Daniel Jacobowitz
2006-06-29 2:27 ` Andrew STUBBS
2006-06-29 3:48 ` Nick Roberts [this message]
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=17569.47799.735812.759914@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=andrew.stubbs@st.com \
--cc=camerons@cse.unsw.edu.au \
--cc=gdb@sourceware.org \
/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