This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
RE: x/i 0x204c5ac. seg fault
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'Shaun Jackman'" <sjackman at gmail dot com>, <gdb at sources dot redhat dot com>
- Date: Fri, 28 Apr 2006 11:25:20 +0100
- Subject: RE: x/i 0x204c5ac. seg fault
On 27 April 2006 19:01, Shaun Jackman wrote:
> The following typo caused a seg fault:
>
> GNU gdb 6.4.50.20060206-cvs
> ...
> (gdb) x/i 0x204c5ac.
> Segmentation fault
>
> Sorry that I haven't tested a more recent version than 6.4.50.20060206-cvs.
Can't reproduce with more recent cvs build on cygwin:
dk@rainbow /usr/build/obj-gdb/gdb> ./gdb /bin/cat
GNU gdb 6.4.50.20060329-cvs
Copyright (C) 2006 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-cygwin"...(no debugging symbols found)
Setting up the environment for debugging gdb.
No symbol table is loaded. Use the "file" command.
No symbol table is loaded. Use the "file" command.
/usr/build/obj-gdb/gdb/.gdbinit:8: Error in sourced command file:
No breakpoint number 0.
(gdb) x/i 0x204c5ac
0x204c5ac: Cannot access memory at address 0x204c5ac
(gdb)
Why not see what happens if you cd into the 'gdb' subdir of your build tree and enter
./gdb ./gdb
and try that command on the inner gdb?
cheers,
DaveK
--
Can't think of a witty .sigline today....