From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit+NEWS 1/2] Add command set/show debug unwind.
Date: Wed, 09 Jan 2013 18:40:00 -0000 [thread overview]
Message-ID: <20130109184045.GG6143@adacore.com> (raw)
In-Reply-To: <20130109124026.GC6415@host2.jankratochvil.net>
> > This patch adds a new debug setting to be used by frame unwinders.
> > It should be relatively straightforward.
>
> is the existing "set debug frame 1" output too disturbing?
> I was using that one already during unwinders debugging.
Actually, why not? Tristan and I discussed it, and we don't
necessarily see a problem with it. I find it a little verbose,
so I'd like to give it a try, and see how it works out. But,
a priori, I think using "set debug frame" would be a good
suggestion.
To answer Tom's question about using zinteger, I think it comes
from what we have been typically using at the time when the code
was written. We had the zinteger vs boolean discussion only
recently... If we prefer staying with the new setting, we will
change it to a boolean.
Thanks for the suggestion!
--
Joel
next prev parent reply other threads:[~2013-01-09 18:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 10:53 Add Windows x64 SEH unwinder (take 2) Joel Brobecker
2013-01-09 10:53 ` [RFA/commit+NEWS 1/2] Add command set/show debug unwind Joel Brobecker
2013-01-09 12:41 ` Jan Kratochvil
2013-01-09 18:40 ` Joel Brobecker [this message]
2013-01-09 15:14 ` Tom Tromey
2013-01-09 16:01 ` Eli Zaretskii
2013-01-09 10:53 ` [RFA/commit+doco 2/2] Windows x64 SEH unwinder Joel Brobecker
2013-01-09 15:52 ` Pedro Alves
2013-01-09 16:28 ` Tristan Gingold
2013-01-09 17:10 ` Pedro Alves
2013-01-09 17:53 ` Tom Tromey
2013-01-09 19:11 ` Pedro Alves
2013-01-09 20:07 ` Tristan Gingold
2013-01-10 16:24 ` Pedro Alves
2013-01-11 8:04 ` Tristan Gingold
2013-07-08 10:55 ` [RFA] Windows x64 SEH unwinder (v2) Tristan Gingold
2013-07-26 15:22 ` Pedro Alves
2013-08-19 13:59 ` Tristan Gingold
2013-08-19 14:13 ` Pedro Alves
2013-08-22 9:33 ` [PATCH v3] Windows x64 SEH unwinder Tristan Gingold
2013-08-22 15:10 ` Eli Zaretskii
2013-08-22 15:26 ` Pedro Alves
2013-08-22 15:41 ` Tristan Gingold
2013-08-22 16:15 ` Pedro Alves
2013-08-23 6:54 ` Tristan Gingold
2013-08-27 17:45 ` Pedro Alves
2013-09-02 9:28 ` Tristan Gingold
2013-01-09 16:06 ` [RFA/commit+doco 2/2] " Eli Zaretskii
2013-01-09 16:29 ` Tristan Gingold
2013-01-09 11:05 ` Add Windows x64 SEH unwinder (take 2) Pedro Alves
2013-01-09 11:11 ` Joel Brobecker
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=20130109184045.GG6143@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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