This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [commit] [patch 2/3] Fix threading internal error on corrupted memory [rediff]
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Date: Wed, 27 Apr 2011 13:36:07 +0100
- Subject: Re: [commit] [patch 2/3] Fix threading internal error on corrupted memory [rediff]
- References: <20110224051354.GB17373@host1.dyn.jankratochvil.net> <20110224073513.GA5851@host1.dyn.jankratochvil.net> <20110417191136.GC3783@host1.jankratochvil.net>
On Sunday 17 April 2011 20:11:36, Jan Kratochvil wrote:
> On Thu, 24 Feb 2011 08:35:13 +0100, Jan Kratochvil wrote:
> > gdb/
> > 2011-02-24 Jan Kratochvil <jan.kratochvil@redhat.com>
> >
> > * linux-thread-db.c (find_new_threads_callback): Exit on zero TI_TID
> > even if !TARGET_HAS_EXECUTION.
> >
> > gdb/testsuite/
> > 2011-02-24 Jan Kratochvil <jan.kratochvil@redhat.com>
> >
> > * gdb.threads/gcore-thread.exp ($core0file): New variable.
> > (clear __stack_user.next, clear stack_used.next)
> > (save a zeroed-threads corefile): New test.
> > Call core_load for $core0file.
> > (zeroed-threads cannot be listed): New test.
I just noticed I'm seeing this (kubuntu 10.10):
info threads
Id Target Id Frame
3 LWP 32326 0x00002aaaab21920d in ?? ()
2 LWP 32379 0x00002aaaab21920d in ?? ()
* 1 LWP 32516 thread2 (arg=0xdeadbeef) at ../../../src/gdb/testsuite/gdb.threads/pthreads.c:91
(gdb) FAIL: gdb.threads/gcore-thread.exp: zeroed-threads cannot be listed
Completely investigated yet. Thought I post it in case this is
something you knew about already.
--
Pedro Alves