From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 623B03858402; Thu, 21 Sep 2023 14:51:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 623B03858402 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1695307879; bh=6aVmSNxgu6LhiooWuEWLZZGh9NVsObzOrvM55TY5W6M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=k3VUDZS7d14sFjb0EkyFWHpdm3XPm01acLhukelDZbCtjaH+bPdKOESul/TLww9PI ULN4M3oFxX11NVnh6+YjrIAFufe/nOFTvOWQNhyRjxxXJeZ9CwBGXWHhnGLD2mmTsE De9k8ZpEZgRDlc8iPqFmAWUj5UBjMbWbZMEvRlFY= From: "dbrumley at forallsecure dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/30847] gdbtypes.c:3355: internal-error causes gdb to abort when setting breakpoint Date: Thu, 21 Sep 2023 14:51:18 +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: 13.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dbrumley at forallsecure dot com X-Bugzilla-Status: UNCONFIRMED 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: In-Reply-To: References: 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=3D30847 --- Comment #5 from David Brumley --- Hi, First, thank=C2=A0you for helping me understand the issue.=C2=A0 Your deep = knowledge and fast response times to something as weird as my bug report are much appreciated. I felt you might be interested in the lecture, and not sure that was useful= for the list. Here are my=C2=A0slides, with the particular CVE starting on page 21: https://docs.google.com/presentation/d/1z_XJWrHgoJrmVcJQHCKth_lx0Olz39e-VXC= _tW9imfk/ * I'm a big believer in the growth mindset, so if you happen to look and see something wrong, please=C2=A0let me know! It's how I get better! * As you can see, I ended up building from source code anyway. Editing the=C2=A0symbol table was pretty easy.=C2=A0 I've done it manually = in the past, but I found a very nice library called lief recently. import lief binary =3D lief.parse('extract75') errno =3D next(filter(lambda e: e.name ( http://e.name/ ) =3D=3D "errno", binary.symbols)) stdin =3D next(filter(lambda e: e.name ( http://e.name/ ) =3D=3D "stdin", binary.symbols)) errno.name ( http://errno.name/ ) =3D stdin.name ( http://stdin.name/ ) binary.write('extract75-hacked') Thanks again! Best wishes, David Dr. David Brumley CEO Executive Assistant: Teressa Peirona < teressa@forallsecure.com > On Wed, Sep 20, 2023 at 7:07 PM, tromey at sourceware dot org < sourceware-bugzilla@sourceware.org > wrote: >=20 >=20 >=20 > https:/ / sourceware. org/ bugzilla/ show_bug. cgi?id=3D30847 ( > https://sourceware.org/bugzilla/show_bug.cgi?id=3D30847 ) >=20 >=20 >=20 > --- Comment #4 from Tom Tromey --- I > totally misread that as you rebuilding your program -- but you rebuilt gdb > (which you said...). > Sorry about that. Anyway this bug is probably not hard to fix, and the > backtrace is handy for diagnosing w/o sources. So, thank you. >=20 >=20 >=20 > -- > You are receiving this mail because: > You reported the bug. >=20 >=20 > --=20 You are receiving this mail because: You are on the CC list for the bug.=