public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r14-4318] libstdc++: Show full Python stack on error
Date: Thu, 28 Sep 2023 20:56:27 +0000 (GMT)	[thread overview]
Message-ID: <20230928205627.F3F2C3858402@sourceware.org> (raw)

https://gcc.gnu.org/g:98db58eb0b8e78708af0770bac1053fa4fcbc5f4

commit r14-4318-g98db58eb0b8e78708af0770bac1053fa4fcbc5f4
Author: Tom Tromey <tromey@adacore.com>
Date:   Wed Sep 27 13:49:59 2023 -0600

    libstdc++: Show full Python stack on error
    
    This changes the libstdc++ test suite to arrange for gdb to show the
    full Python stack if any sort of Python exception occurs.  This makes
    debugging the printers a little simpler.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/lib/gdb-test.exp (gdb-test): Enable Python
            stack traces from gdb.

Diff:
---
 libstdc++-v3/testsuite/lib/gdb-test.exp | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/libstdc++-v3/testsuite/lib/gdb-test.exp b/libstdc++-v3/testsuite/lib/gdb-test.exp
index d8e572ef7b3..af7d970d388 100644
--- a/libstdc++-v3/testsuite/lib/gdb-test.exp
+++ b/libstdc++-v3/testsuite/lib/gdb-test.exp
@@ -141,6 +141,8 @@ proc gdb-test { marker {selector {}} {load_xmethods 0} } {
     puts $fd "set auto-load no"
     # Now that we've disabled auto-load, it's safe to set the target file
     puts $fd "file ./$output_file"
+    # See the full backtrace of any failures.
+    puts $fd "set python print-stack full"
     # Load & register *our* copy of the pretty-printers
     puts $fd "source $printer_code"
     puts $fd "python register_libstdcxx_printers(None)"

                 reply	other threads:[~2023-09-28 20:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230928205627.F3F2C3858402@sourceware.org \
    --to=tromey@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@gcc.gnu.org \
    /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).