Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Joshua Watt <jpewdev@gmail.com>, gdb@sourceware.org
Subject: Re: Option to disable frame checking
Date: Mon, 01 Oct 2012 17:26:00 -0000	[thread overview]
Message-ID: <20121001172618.GA23158@host2.jankratochvil.net> (raw)
In-Reply-To: <20121001172117.GG30746@adacore.com>

On Mon, 01 Oct 2012 19:21:17 +0200, Joel Brobecker wrote:
> > Is it acceptable to make a patch that allows this check to be turned
> > off (i.e. "set frame-inner-check off" or similar), or is there another
> > method that is more acceptable?
> 
> Knowing that the Go language makes extensive use of alternate stacks,
> I think it's just better to remove the check altogether.

I do not know about Go alternate stacks but the checks for example already
supports gcc -fsplit-stack.  More such features should be rather implemented
than to drop UNWIND_INNER_ID.  Could not be GDB taught about thue alternate
stack?

Looping backtraces are a pain for both interactive and automatic bugreporting,
it is already a TODO item GDB should better handle f() { f(); } type stack
overflows as it proven less GDB-savvy users fail to debug such issue in GDB.


Thanks,
Jan


  reply	other threads:[~2012-10-01 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 17:04 Joshua Watt
2012-10-01 17:21 ` Joel Brobecker
2012-10-01 17:26   ` Jan Kratochvil [this message]
2012-10-01 17:59     ` Joel Brobecker
2012-10-01 18:39     ` Joshua Watt
2012-10-01 18:54       ` Jan Kratochvil

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=20121001172618.GA23158@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=jpewdev@gmail.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