public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug dap/30686] [gdb/dap] ERROR: eof reading json header in gdb.dap/cond-bp.exp
Date: Wed, 26 Jul 2023 17:38:04 +0000 [thread overview]
Message-ID: <bug-30686-4717-sg527Obt5H@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30686-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30686
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
I was able to reproduce this.
No idea what is going on here.
My stack trace is a bit different:
#3 0x000000000078825d in handle_sigsegv (sig=11)
at ../../binutils-gdb/gdb/event-top.c:962
#4 <signal handler called>
#5 0x00007f7eb3400731 in _PyUnicode_Ready () from /lib64/libpython3.10.so.1.0
#6 0x00007f7eb3270513 in _PyUnicode_JoinArray.cold ()
from /lib64/libpython3.10.so.1.0
#7 0x00007f7eb332af01 in PyUnicode_Join () from /lib64/libpython3.10.so.1.0
#8 0x00007f7eb33f9252 in join_list_unicode () from /lib64/libpython3.10.so.1.0
#9 0x00007f7eb3408faa in flush_accumulator () from /lib64/libpython3.10.so.1.0
#10 0x00007f7eb3408f40 in _PyAccu_FinishAsList ()
from /lib64/libpython3.10.so.1.0
...
Nothing interesting in the various logs.
I wonder if valgrind would say something.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-26 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 14:16 [Bug dap/30686] New: " vries at gcc dot gnu.org
2023-07-26 14:18 ` [Bug dap/30686] " vries at gcc dot gnu.org
2023-07-26 14:44 ` vries at gcc dot gnu.org
2023-07-26 15:02 ` vries at gcc dot gnu.org
2023-07-26 17:38 ` tromey at sourceware dot org [this message]
2023-07-26 20:29 ` tromey at sourceware dot org
2023-07-27 13:41 ` tromey at sourceware dot org
2023-07-27 13:59 ` tromey at sourceware dot org
2023-07-27 13:59 ` tromey at sourceware dot org
2023-07-28 12:18 ` cvs-commit at gcc dot gnu.org
2023-07-28 12:19 ` 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-30686-4717-sg527Obt5H@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: 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).