From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 90CD53858C78; Sun,  6 Mar 2022 18:30:08 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 90CD53858C78
From: "r.kloos at campus dot tu-berlin.de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27317] gdb crashes upon target remote :1234
Date: Sun, 06 Mar 2022 18:30:08 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: 9.2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: r.kloos at campus dot tu-berlin.de
X-Bugzilla-Status: WAITING
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: 
Message-ID: <bug-27317-4717-KpDz4GkgQr@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-27317-4717@http.sourceware.org/bugzilla/>
References: <bug-27317-4717@http.sourceware.org/bugzilla/>
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
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Mar 2022 18:30:08 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D27317

--- Comment #5 from r.kloos at campus dot tu-berlin.de ---
(In reply to Tom Tromey from comment #3)
> A core dump of gdb isn't super useful, because it's specific
> to your build of gdb.  The failing executable might be useful
> if the problem can be reproduced without any special setup
> (maybe not in this case).  A stack trace from gdb itself might
> also be informative.

Apart from the backtrace I could also upload the executable, but I am not s=
ure
if it would be helpful without the rest of the code.
It's kernel code from a university course running on qemu, so reproducing t=
he
bug would need a special setup software wise.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=