public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29968] New: [gdb/dap] silent exceptions when using DAP Date: Fri, 06 Jan 2023 13:53:54 +0000 [thread overview] Message-ID: <bug-29968-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29968 Bug ID: 29968 Summary: [gdb/dap] silent exceptions when using DAP Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- When reproducing the problem fixed by commit 954a1f9183c ("[gdb/python] Avoid queue.SimpleQueue for python 3.6"), by reverting the commit, I get: ... $ gdb -q -i dap $ ... So gdb, just exits. By echoing the exit status I get confirmation that indeed something is wrong: ... $ gdb -q -i dap; echo $? 1 $ ... Only by debugging and doing catch throw do I find out that I'm running into a python exception. It would be nice if gdb would somehow print exceptions. By doing catch catch do I see that indeed exception_print is called in gdb_main: ... 1329 exception_print (gdb_stderr, ex); ... with the exception ex containing the desired message, but that seems to have no visible effect. I tried some obvious-looking things after executing the exception_print, trying to get the printed text to somehow appear: ... (gdb) call (void)fflush (0) (gdb) call gdb_flush (*current_ui_gdb_stderr_ptr ()) (gdb) call gdb_flush (*current_ui_gdb_stdout_ptr ()) (gdb) call (void)fflush (0) ... but no luck. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-01-06 13:53 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-06 13:53 vries at gcc dot gnu.org [this message] 2023-01-06 14:04 ` [Bug gdb/29968] " vries at gcc dot gnu.org 2023-01-06 19:34 ` tromey at sourceware dot org
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=bug-29968-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).