Subject: bin/4590: gdb on pmax cannot handle stripped binaries
To: None <email@example.com>
From: Jonathan Stone <jonathan@DSG.Stanford.EDU>
Date: 11/27/1997 17:58:36
>Synopsis: stack traceback fails on stripped binaries.
>Responsible: bin-bug-people (Utility Bug People)
>Arrival-Date: Thu Nov 27 18:05:01 1997
>Originator: Jonathan Stone
>Release: NetBSD 1.3_ALPHA as at Nov 26 1997
System: NetBSD Reno.DSG.Stanford.EDU 1.3_ALPHA NetBSD 1.3_ALPHA (GENERIC) #0: Sat Nov 22 16:32:51 PST 1997 jonathan@Reno.DSG.Stanford.EDU:/reno/compile/GENERIC pmax
gdb on pmaxes cannot handles tatic binaries.
Even a hex-address stacktrace fails.
GDB reports that the heuristic fencepost on its PC search is
exceeded and gives up.
This used to work with stock FSF gdb 4.16.
Get a stripped static binary to coredump. (early 1.3_ALPHA sysinst on
a large scree was a good candidate). Ask for a stack traceback and
Observe the `heuristic fencepost exceeded' warning.
I'm just guessing but it looks like the PC that gdb is getting from
the coredump is wrong.
Stack traceback of live inferiors (even when stripped) used to work on
the pre-integrated gdb 4.16 (and 4.15) code shipped with NetBSD/pmax