This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: threads/2149: thread_db_get_info: cannot get thread info: genericerror on fork()/execvp()
- From: "Matthew M. DeLoera" <mdeloer at aol dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 1 Aug 2006 16:38:02 -0000
- Subject: Re: threads/2149: thread_db_get_info: cannot get thread info: genericerror on fork()/execvp()
- Reply-to: "Matthew M. DeLoera" <mdeloer at aol dot com>
The following reply was made to PR threads/2149; it has been noted by GNATS.
From: "Matthew M. DeLoera" <mdeloer@aol.com>
To: gdb-gnats@sources.redhat.com
Cc: alex@alex.org.uk, drow@false.org
Subject: Re: threads/2149: thread_db_get_info: cannot get thread info: generic
error on fork()/execvp()
Date: Tue, 01 Aug 2006 12:32:00 -0400
Thanks for the quick response.
I downloaded, built, installed, and ran gdb-6.5.50.20060801.tar.bz2 - I
ran .configure, make, and make install. When I ran gdb, I saw "GNU gdb
6.5.50.20060801".
Unfortunately, it's still not working. When I attempt a fork after a
thread has previously ended, gdb responds with "Couldn't get registers:
No such process.".
I also made sure that follow-fork-mode was still set to parent. For the
record, I don't have a need to follow the child anyway. I want to stay
with the parent.
Thanks!
- Matthew