RE: A couple of small problems
Kip Macy <[email protected]>
| Newsgroups | gmane.linux.ngpt.devel |
|---|---|
| Message-ID | <Pine.GSO.4.10.10212171427210.8440-100000@elwood> |
What kernel version are you using? I'll roll back to 2.4.18, if you are using that without problems. It is always possible that my applying the tcore patch by hand to the 2.4.19 tree had side effects. That seems unlikely. hershey% export GDB_LIBTHREAD_DB=/usr/lib/libthread_db.so.1 hershey% pwd /u/kmacy/tmp/gdb-5.2 hershey% r gdb/gdb ~/p4/ontap/linuxdev/prod/build/maytag.Ld 24033 GNU gdb 5.2 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 "i686-pc-linux-gnu"... Attaching to program: /x/eng/build6/scratch/kmacy/linuxdev.13542.331_20_54_08/prod/build/maytag.Ld, process 24033 Reading symbols from /usr/lib/libpthread.so.20...done. lin-lwp.c:1034: gdb-internal-error: lin_lwp_wait: Assertion `num_lwps == 0 || iterate_over_lwps (resumed_callback, NULL)' failed. An internal GDB error was detected. This may make further debugging unreliable. Quit this debugging session? (y or n) Please answer y or n. An internal GDB error was detected. This may make further debugging unreliable. Quit this debugging session? (y or n) y Create a core file containing the current state of GDB? (y or n) n hershey% uname -a Linux hershey.eng.netapp.com 2.4.19 #2 SMP Mon Dec 16 16:06:28 PST 2002 i686 i686 i386 GNU/Linux -Kip On Tue, 17 Dec 2002, Howell, David P wrote: > I'll try to duplicate this here, I haven't seen this failure with > attach. > It has worked in the cases that I've tried, however I have always used > the > 'gdb-ngpt exe 123' form to do my attaches. I will try the internal > attach > to see if there isn't something different going on. It would be > interesting > to see if you are seeing the same failure doing it this way. > > Dave Howell > > -----Original Message----- > From: Kip Macy [mailto:[email protected]] > Sent: Tuesday, December 17, 2002 1:52 AM > To: Gross, Mark > Cc: Howell, David P; [email protected] > Subject: RE: [pthreads-devel] A couple of small problems > > I reworked the patch to apply cleanly to 2.4.19. It works fine for my > purposes. > However, GDB isn't just crippled when it comes to looking at ULT in a > core-file, > it isn't able to attach to a running process without hitting an > assertion > failure. Any suggestions on what to do to fix this? > > > [kmacy@hershey ~/gdb-5.2]$ sudo /usr/netapp/bin/gdb-ngpt > ~/p4/ontap/linuxdev/prod/build/maytag.Ld > GNU gdb 5.2 > 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 "i686-pc-linux-gnu"...attach 6904 > > (gdb) attach 6904 > Attaching to program: > /x/eng/build6/scratch/kmacy/linuxdev.13542.331_20_54_08/prod/build/mayta > g.Ld, > process 6904 > Reading symbols from /usr/lib/libpthread.so.20...done. > lin-lwp.c:1034: gdb-internal-error: lin_lwp_wait: Assertion `num_lwps == > 0 || > iterate_over_lwps (resumed_callback, NULL)' failed. > An internal GDB error was detected. This may make further > debugging unreliable. Quit this debugging session? (y or n) > > > -Kip >