On Sat, Mar 21, 2009 at 04:59:34PM +0100, Claus Fischer wrote:
With the latest gdb, a watchpoint which points into allocated memory
that is not available at process start, will not only cause the
program but also gdb to crash and abort.
Can you show me an example debug session where this
Here is an example that works for me.
Environment:
Debian Lenny amd64
8 GB RAM (probably doesn't matter)
Linux 2.6.26-1-amd64
echo 0 /proc/sys/kernel/randomize_va_space # important!
linux-image-amd64 2.6.26+17
gcc 4:4.3.2-2
gdb 6.8-3
emacs 22.2+2-5
Code:
On Sun, Mar 22, 2009 at 03:04:23PM +0100, Claus Fischer wrote:
r# gives the following output
-
Starting program: /home/cfischer/tmp/tt
Error in re-setting breakpoint 3: Cannot access memory at address
0x777e2f90
Error in re-setting
On Sun, Mar 22, 2009 at 01:45:59PM -0400, Daniel Jacobowitz wrote:
: My mistake: I have the GDB from experimental installed. It works
: there. I need to update unstable.
The problem as I experience is on Lenny. Haven't tried experimental
or unstable (yet).
Claus
--
Claus Fischer
Package: gdb
Version: 6.8-3
Summary: The latest gdb will usually crash as a consequence of a
watchpoint outside the process's memory range. Older gdb's
would sometimes try to disable the watchpoint instead.
In a debugging session of a large program, it is often necessary
to
5 matches
Mail list logo
