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 7089A3858C39; Mon, 21 Feb 2022 12:06:23 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7089A3858C39
From: "aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/28900] GDB crash on loading symbols form openbios binary
Date: Mon, 21 Feb 2022 12:06:23 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: symtab
X-Bugzilla-Version: 11.2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aburgess at redhat dot com
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: 
Message-ID: <bug-28900-4717-b2LEH1mRCs@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28900-4717@http.sourceware.org/bugzilla/>
References: <bug-28900-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: Mon, 21 Feb 2022 12:06:23 -0000

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

--- Comment #11 from Andrew Burgess <aburgess at redhat dot com> ---
With commit 336125713fc GDB should no longer crash, but this is achieved by
just ignoring the symbols stabs data that we don't currently know how to
handle.

If you do 'set complaints 1000' before loading the offending binary into GD=
B,
then you get to see GDB complain about all the debug symbols it can't handl=
e.=20
The output looks like:

  During symbol reading: function `_savegpr_14' appears to be defined outsi=
de
of all compilation units
  During symbol reading: function `_save32gpr_14' appears to be defined out=
side
of all compilation units
  During symbol reading: function `_savegpr_15' appears to be defined outsi=
de
of all compilation units
  ... snip ...
  During symbol reading: function `_restgpr_14' appears to be defined outsi=
de
of all compilation units
  During symbol reading: function `_rest32gpr_14' appears to be defined out=
side
of all compilation units
  During symbol reading: function `_restgpr_15' appears to be defined outsi=
de
of all compilation units
  ... snip ...

Which look like register save/restore hooks, but I don't claim to really
understand.  I don't believe that these symbols have and DWARF information
available, so these functions will not show up in something like 'info
functions', but there is a symbol for these functions in the symbol table,
which GDB does read, so you can do things like 'x/10i _savegpr_14`, however,
the symbol table entry has no type or size, so GDB doesn't understand the
bounds of the function.

Given the original bug description is for GDB crashing, and this is now fix=
ed.=20
I'd like to tentatively propose we close this bug.  If Glenn feels like the=
re
is still important debug information that isn't being loaded, this might be
better represented in a new bug.  Given the lack of GDB developers interest=
ed
in improving stabs support (right now), I suspect any new bug is not likely=
 to
get much attention.  Thoughts?

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