public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/29968] New: [gdb/dap] silent exceptions when using DAP
@ 2023-01-06 13:53 vries at gcc dot gnu.org
2023-01-06 14:04 ` [Bug gdb/29968] " vries at gcc dot gnu.org
2023-01-06 19:34 ` tromey at sourceware dot org
0 siblings, 2 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2023-01-06 13:53 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug gdb/29968] [gdb/dap] silent exceptions when using DAP
2023-01-06 13:53 [Bug gdb/29968] New: [gdb/dap] silent exceptions when using DAP vries at gcc dot gnu.org
@ 2023-01-06 14:04 ` vries at gcc dot gnu.org
2023-01-06 19:34 ` tromey at sourceware dot org
1 sibling, 0 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2023-01-06 14:04 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29968
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug gdb/29968] [gdb/dap] silent exceptions when using DAP
2023-01-06 13:53 [Bug gdb/29968] New: [gdb/dap] silent exceptions when using DAP vries at gcc dot gnu.org
2023-01-06 14:04 ` [Bug gdb/29968] " vries at gcc dot gnu.org
@ 2023-01-06 19:34 ` tromey at sourceware dot org
1 sibling, 0 replies; 3+ messages in thread
From: tromey at sourceware dot org @ 2023-01-06 19:34 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29968
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I don't think gdb can really print anything, because
the output has to follow the JSON-RPC protocol.
Previously I had this mode not redirect stderr,
but that turned out not to work with the client we're using.
There is a logging setting that the test suite uses though.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-01-06 19:34 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-06 13:53 [Bug gdb/29968] New: [gdb/dap] silent exceptions when using DAP vries at gcc dot gnu.org
2023-01-06 14:04 ` [Bug gdb/29968] " vries at gcc dot gnu.org
2023-01-06 19:34 ` tromey at sourceware dot org
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).