This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: gdb/2036: cannot access errno when debugging core files createdwith gcore on GNU/Linux (RHEL-3, gdb 6.0post-0.20031117.6rh and GNU gdb 6.3)
- From: Mike Zraly <Michael dot Zraly at openwave dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 25 Nov 2005 13:08:01 -0000
- Subject: Re: gdb/2036: cannot access errno when debugging core files createdwith gcore on GNU/Linux (RHEL-3, gdb 6.0post-0.20031117.6rh and GNU gdb 6.3)
- Reply-to: Mike Zraly <Michael dot Zraly at openwave dot com>
The following reply was made to PR gdb/2036; it has been noted by GNATS.
From: Mike Zraly <Michael.Zraly@openwave.com>
To: gdb-gnats@sources.redhat.com, nobody@sources.redhat.com,
Michael.Zraly@openwave.com, gdb-prs@sources.redhat.com
Cc:
Subject: Re: gdb/2036: cannot access errno when debugging core files created
with gcore on GNU/Linux (RHEL-3, gdb 6.0post-0.20031117.6rh and GNU gdb 6.3)
Date: Fri, 25 Nov 2005 08:02:42 -0500
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view audit-trail
Additional information:
I also cannot access errno when degugging core files created by the OS
due to SIGABRT. gdb gives me the same error message as before:
Cannot access memory at address 0xb6e8c008
I'm not sure at this point if the error is in gdb or in the OS,
or both.
- Mike