Subject: toolchain/32076: gdb can not attach to processes
To: None <toolchain-manager@netbsd.org, gnats-admin@netbsd.org,>
From: Martin Husemann <martin@aprisoft.de>
List: netbsd-bugs
Date: 11/15/2005 07:41:00
>Number: 32076
>Category: toolchain
>Synopsis: gdb can not attach to processes
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: toolchain-manager
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Nov 15 07:41:00 +0000 2005
>Originator: Martin Husemann
>Release: NetBSD 3.99.11
>Organization:
>Environment:
System: NetBSD nelly.aprisoft.de 3.99.11 NetBSD 3.99.11 (NELLY) #0: Mon Nov 7 10:16:13 CET 2005 martin@nelly.aprisoft.de:/usr/src/sys/arch/sparc64/compile/NELLY sparc64
Architecture: sparc64
Machine: sparc64
>Description:
Trying to debug a running process with gdb -p does not work on sparc64:
$ gdb -p 4220
GNU gdb 5.3nb1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "sparc64--netbsdelf".
Attaching to process 4220
/usr/src/gnu/dist/gdb/gdb/solib-svr4.c:1282: gdb-internal-error: legacy_fetch_link_map_offsets called without legacy link_map support enabled.
An internal GDB error was detected. This may make further
debugging unreliable. Quit this debugging session? (y or n) n
Create a core file containing the current state of GDB? (y or n) n
>How-To-Repeat:
s/a
>Fix:
no idea