From: Tom Tromey <tom@tromey.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
Stefan Hajnoczi via Gdb <gdb@sourceware.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, pedro@palves.net,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: How to backtrace an separate stack?
Date: Wed, 09 Mar 2022 12:50:22 -0700 [thread overview]
Message-ID: <87fsnqgb29.fsf@tromey.com> (raw)
In-Reply-To: <87ilsn784k.fsf@oldenburg.str.redhat.com> (Florian Weimer's message of "Wed, 09 Mar 2022 11:06:19 +0100")
>> Yes, the infamous "previous frame inner to this frame" error message. I
>> think this is primarily intended to detect stack trashing, but maybe it
>> also serves to work around bad debuginfo or bugs in the unwinders.
Florian> Is there a user-level command to disable the check manually?
I don't think so. I think it would be fine if someone wanted to add
one.
Tom
next prev parent reply other threads:[~2022-03-09 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 11:22 Stefan Hajnoczi
2022-03-07 10:49 ` Pedro Alves
2022-03-08 9:47 ` Stefan Hajnoczi
2022-03-07 14:49 ` Florian Weimer
2022-03-07 17:30 ` Tom Tromey
2022-03-09 10:06 ` Florian Weimer
2022-03-09 19:50 ` Tom Tromey [this message]
2022-03-07 16:58 ` Tom Tromey
2022-03-07 17:18 ` Pedro Alves
2022-03-08 8:43 ` Stefan Hajnoczi
2022-03-14 20:30 ` Tom Tromey
2022-03-15 14:17 ` Stefan Hajnoczi
2022-03-18 21:13 ` Tom Tromey
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=87fsnqgb29.fsf@tromey.com \
--to=tom@tromey.com \
--cc=dgilbert@redhat.com \
--cc=fweimer@redhat.com \
--cc=gdb@sourceware.org \
--cc=pedro@palves.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).