All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: Stefan Hajnoczi via Gdb <gdb@sourceware.org>,
	pedro@palves.net, qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: How to backtrace an separate stack?
Date: Wed, 09 Mar 2022 11:06:19 +0100	[thread overview]
Message-ID: <87ilsn784k.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87fsnt1xhg.fsf@tromey.com> (Tom Tromey's message of "Mon, 07 Mar 2022 10:30:35 -0700")

* Tom Tromey:

> Florian> I'm a bit surprised by this.  Conceptually, why would GDB need to know
> Florian> about stack boundaries?  Is there some heuristic to detect broken
> Florian> frames?
>
> 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.
>
> This error was disabled for cases where the GCC split stack feature is
> used.  There's been requests to disable it in other cases as well, I
> think.

Is there a user-level command to disable the check manually?

Thanks,
Florian



  reply	other threads:[~2022-03-09 10:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 11:22 How to backtrace an separate stack? 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 [this message]
2022-03-09 19:50       ` Tom Tromey
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=87ilsn784k.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=pedro@palves.net \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=tom@tromey.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.