From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add debug output for the skip feature
Date: Wed, 12 Sep 2018 13:10:00 -0000 [thread overview]
Message-ID: <6c34a5f57324f991d7eec89d2e52b48d@polymtl.ca> (raw)
In-Reply-To: <dad3b3e6-e621-b37e-3867-7570c994ff40@redhat.com>
On 2018-09-11 07:16, Pedro Alves wrote:
> On 09/11/2018 12:03 PM, Simon Marchi wrote:
>> While trying to create skips for libstdc++, I found myself debugging
>> GDB
>> quite a bit, mostly to find out what the exact function name to match
>> is. I thought it would make sense to have this information as debug
>> output.
>>
>> This patch adds "set debug skip on|off".
>
> Needs manual/NEWS changes.
Damn, I really need a git send-email hook that asks me whether my patch
needs a manual or NEWS update.
Thanks for reminding me.
Simon
next prev parent reply other threads:[~2018-09-12 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 11:04 Simon Marchi
2018-09-11 11:16 ` Pedro Alves
2018-09-12 13:10 ` Simon Marchi [this message]
2018-09-12 13:12 ` [PATCH v2 (doc)] " Simon Marchi
2018-09-12 14:25 ` Eli Zaretskii
2018-09-12 16:27 ` Simon Marchi
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=6c34a5f57324f991d7eec89d2e52b48d@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.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