From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0F0333858D33; Fri, 6 Jan 2023 13:53:55 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0F0333858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673013235; bh=liQISJrql8yuAxK6J9LqedyyYJgDYNoc1FHx0KHZoiw=; h=From:To:Subject:Date:From; b=OqXedayQbwSeufBnP1LolWW2Tp65gG0X8fPNysAViuRQCyld9apTcpVZBBHVcKxow WlR9ArH2BmT/RgX/V8fxbT5eHCTyD4NdHIquV20CFeY28McO4vh8z4RqDb9uRJlKnO vvBbNhwtQlUtfdjWCPjendaRxvKMy5vry3ljwdnI= From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29968 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] Avo= id 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 wron= g: ... $ 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 hav= e no visible effect. I tried some obvious-looking things after executing the exception_print, tr= ying 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=