This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

pending/2262: Subject=Re%3A%20gdb%2F2238%3A%20assertion%20failure%20in%20linux_nat_attach%28%29%20when%20attaching%20to%20a%20hung%20Xorg%20instance

From: Juergen Leising <juergen dot leising at gmx dot de>
To: gdb-gnats at sources dot redhat dot com
Date: Wed, 16 May 2007 17:11:34 +0200
Subject: pending/2262: Subject=Re%3A%20gdb%2F2238%3A%20assertion%20failure%20in%20linux_nat_attach%28%29%20when%20attaching%20to%20a%20hung%20Xorg%20instance

>Number:         2262
>Category:       pending
>Synopsis:       Subject=Re%3A%20gdb%2F2238%3A%20assertion%20failure%20in%20linux_nat_attach%28%29%20when%20attaching%20to%20a%20hung%20Xorg%20instance
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   unknown
>Arrival-Date:   Wed May 16 15:18:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 Same with me, while applying valgrind-2.3 on a third program. 
 The third program had memory errors. valgrind was to attach
 gdb on the running program by
 
              /usr/bin/gdb -nw /proc/22000/fd/1014 22000
 
 I have
 
 gdb-6.6 (built from tar.bz2, not any rpm version)
 AMD Sempron(tm) Processor 3000+,
 kernel 2.6.18-1.2798.fc6,
 fedora core 6,
 glibc-2.5
 
 The wait status was:
 
 (top-gdb) print status
 $5 = 127
 
 Best regards,
 
 Juergen
 
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]