From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joshua Watt <jpewdev@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: Option to disable frame checking
Date: Mon, 01 Oct 2012 18:54:00 -0000 [thread overview]
Message-ID: <20121001185353.GA6119@host2.jankratochvil.net> (raw)
In-Reply-To: <CAEPrYjTa1t4bGJBEq-pvm2z2hwt597Mo11LP4zCVe58pA1yxwA@mail.gmail.com>
On Mon, 01 Oct 2012 20:38:54 +0200, Joshua Watt wrote:
> I'm not sure how that would be accomplished. AFAIK, there isn't any sort of
> information in the DWARF debugging format that could be used to (definitively)
> indicate the thread has jumped stacks, so I think it would have to be determined
> by something external to the code being debugged. I think that such a heuristic
> approach could be difficult to get correct in all cases,
In such case the "alternate stack" feature is insufficiently designed and it
should be extended for its debuggability. Debuggability is a normal
associated part of any new ABI feature.
> hence the idea of making it a user configurable option.
Every user configurable option is just a last resort workaround. In the best
world there would be no configuration options, ever.
> I won't claim to be an expert in the DWARF debugging format though,
It does not always have to be in DWARF. For example the gcc -fsplit-stack did
not need any DWARF extensions (it was enough to verify specific ELF symbol).
http://sourceware.org/git/?p=gdb.git;a=commitdiff;h=457da755a718113dcbc339f7823af0d439fa62c7
Thanks,
Jan
prev parent reply other threads:[~2012-10-01 18:54 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
2012-10-01 17:59 ` Joel Brobecker
2012-10-01 18:39 ` Joshua Watt
2012-10-01 18:54 ` Jan Kratochvil [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=20121001185353.GA6119@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).