From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb, c++] Improve error message when using libstdcxx without SDT probes
Date: Mon, 26 Aug 2019 14:11:00 -0000 [thread overview]
Message-ID: <87h86410g2.fsf@redhat.com> (raw)
In-Reply-To: <20190725210447.GA26123@delia> (Tom de Vries's message of "Thu, 25 Jul 2019 23:04:49 +0200")
On Thursday, July 25 2019, Tom de Vries wrote:
> Hi,
>
> When using catch catch/rethrow/catch, a libstdcxx with SDT probes is required
> for both the regexp argument, and the convenience variable $_exception (
> https://sourceware.org/gdb/current/onlinedocs/gdb/Set-Catchpoints.html ).
>
> Currently, when using these features with a libstdcxx without SDT probes, we
> get the cryptic error message:
> ...
> not stopped at a C++ exception catchpoint
> ...
>
> Improve this by instead emitting the more helpful:
> ...
> did not find exception probe (does libstdcxx have SDT probes?)
> ...
>
> Tested on x86_64-linux.
>
> OK for trunk?
Thanks for the patch.
> Thanks,
> - Tom
>
> [gdb, c++] Improve error message when using libstdcxx without SDT probes
>
> gdb/ChangeLog:
>
> 2019-07-25 Tom de Vries <tdevries@suse.de>
>
> PR c++/24852
> * break-catch-throw.c (fetch_probe_arguments): Improve error mesage
> when pc_probe.prob == NULL.
>
> gdb/testsuite/ChangeLog:
>
> 2019-07-25 Tom de Vries <tdevries@suse.de>
>
> PR c++/24852
> * gdb.cp/no-libstdcxx-probe.exp: New test.
>
> ---
> gdb/break-catch-throw.c | 6 ++-
> gdb/testsuite/gdb.cp/no-libstdcxx-probe.exp | 58 +++++++++++++++++++++++++++++
> 2 files changed, 62 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/break-catch-throw.c b/gdb/break-catch-throw.c
> index 0677a55ee5..2d91285312 100644
> --- a/gdb/break-catch-throw.c
> +++ b/gdb/break-catch-throw.c
> @@ -106,8 +106,10 @@ fetch_probe_arguments (struct value **arg0, struct value **arg1)
> unsigned n_args;
>
> pc_probe = find_probe_by_pc (pc);
> - if (pc_probe.prob == NULL
> - || pc_probe.prob->get_provider () != "libstdcxx"
> + if (pc_probe.prob == NULL)
> + error (_("did not find exception probe (does libstdcxx have SDT probes?)"));
> +
> + if (pc_probe.prob->get_provider () != "libstdcxx"
> || (pc_probe.prob->get_name () != "catch"
> && pc_probe.prob->get_name () != "throw"
> && pc_probe.prob->get_name () != "rethrow"))
> diff --git a/gdb/testsuite/gdb.cp/no-libstdcxx-probe.exp b/gdb/testsuite/gdb.cp/no-libstdcxx-probe.exp
> new file mode 100644
> index 0000000000..4c1a706ae0
> --- /dev/null
> +++ b/gdb/testsuite/gdb.cp/no-libstdcxx-probe.exp
> @@ -0,0 +1,58 @@
> +# Copyright 2019 Free Software Foundation, Inc.
> +
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 3 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program. If not, see <http://www.gnu.org/licenses/>.
> +
> +standard_testfile exceptprint.cc
> +
> +if {[skip_cplus_tests]} {
> + return -1
> +}
> +
> +if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug c++}]} {
> + return -1
> +}
> +
> +if {![runto_main]} {
> + return -1
> +}
> +
> +set libstdcxx_probe_tests_supported [skip_libstdcxx_probe_tests]
Not your fault, but this reversed logic (skip_libstdcxx_probe_tests
returns 0 if the tests should be skipped) is kinda confusing.
> +
> +if { $libstdcxx_probe_tests_supported == 1 } {
> + untested "Have libstdc++ stap probe"
> + return -1
> +}
> +
> +proc do_continue_to_catchpoint {name} {
> + global gdb_prompt
> +
> + gdb_test_multiple "continue" $name {
> + -re "Continuing.*Catchpoint \[0-9\].*\r\n$gdb_prompt $" {
You can use $decimal instead of \[0-9\] if you want.
> + pass $name
> + }
> + }
> +}
> +
> +proc do_exceptprint_tests {prefix output} {
> + with_test_prefix $prefix {
> + do_continue_to_catchpoint "continue to throw"
> + gdb_test "print \$_exception" \
> + "did not find exception probe \\(does libstdcxx have SDT probes\\?\\).*"
> + }
> +}
You don't seem to use $output here.
> +
> +gdb_test "catch throw" "Catchpoint \[0-9\]+ \\(throw\\)" \
> + "catch throw"
$decimal if you want.
> +
> +do_exceptprint_tests string "$hex \"hi bob\""
The patch looks good to me. Thanks for doing this.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2019-08-26 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 21:04 Tom de Vries
2019-07-26 21:00 ` Tom Tromey
2019-08-13 13:51 ` [PING][PATCH][gdb, " Tom de Vries
2019-08-26 8:47 ` [PING^2][PATCH][gdb, " Tom de Vries
2019-08-26 14:11 ` Sergio Durigan Junior [this message]
2019-08-26 16:51 ` [committed][gdb/testsuite] Make skip_libstdcxx_probe_tests return 1 if true Tom de Vries
2019-08-26 17:02 ` Sergio Durigan Junior
2019-08-26 17:27 ` [PATCH][gdb, c++] Improve error message when using libstdcxx without SDT probes Tom de Vries
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=87h86410g2.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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