This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: symtab/2161: Debug Info|ELF| GDB shows memory as being mapped when it might not be
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 28 Aug 2006 00:48:01 -0000
- Subject: Re: symtab/2161: Debug Info|ELF| GDB shows memory as being mapped when it might not be
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR symtab/2161; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: alex00882007@gmail.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: symtab/2161: Debug Info|ELF| GDB shows memory as being mapped when it might not be
Date: Sun, 27 Aug 2006 20:41:45 -0400
On Mon, Aug 28, 2006 at 12:14:03AM -0000, alex00882007@gmail.com wrote:
> The program crashes when it tries to read from this memory address.
> (Just in case I also tried to mprotect it to make sure it wasnt just
> not marked readable in some strange twist)
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0804846c in main ()
> (gdb) x/i $eip
> 0x804846c <main+144>: mov (%eax),%eax
> (gdb) x/wx $eax
> 0x904d000 <completed.4463+16791820>: 0x44434241
GDB 6.4 shouldn't generally read memory in unmapped areas, though other
versions (earlier and later) might; do you have a sample app which
might show this behavior that you could attach?
--
Daniel Jacobowitz
CodeSourcery