system/3922: gdb --pid is totally broken in OpenBSD 3.6

[Frank Denis <j@pureftpd.org>]

>Number:         3922
>Category:       system
>Synopsis:       gdb --pid is totally broken in OpenBSD 3.6
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Sep 11 12:40:01 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Jedi/Sector One
>Release:        3.6
>Organization:
net
>Environment:
	System      : OpenBSD 3.6
	Architecture: OpenBSD.i386
	Machine     : i386
>Description:
It looks like gdb --pid=... doesn't work any more on OpenBSD 3.6 / i386
>How-To-Repeat:

$ sudo gdb --pid=28630
GNU gdb 6.1
Copyright 2004 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 "i386-unknown-openbsd3.6".
Attaching to process 28630
/usr/src/gnu/usr.bin/binutils/gdb/solib-svr4.c:1443: internal-error: legacy_fetch_link_map_offsets called without legacy link_map support enabled.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) b n

/usr/src/gnu/usr.bin/binutils/gdb/solib-svr4.c:1443: internal-error: legacy_fetch_link_map_offsets called without legacy link_map support enabled.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
0x017f0b39 in ?? ()
(gdb) where
#0  0x017f0b39 in ?? ()
#1  0x1c0018d5 in ?? ()
#2  0x00000000 in ?? ()


>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: