This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

breakpoints/2067: gdb could disable address randomization for inferior


>Number:         2067
>Category:       breakpoints
>Synopsis:       gdb could disable address randomization for inferior
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 09 06:38:01 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Tom Tromey <tromey@redhat.com>
>Release:        6.3
>Organization:
>Environment:

>Description:
I'm using x86 FC4 Linux.  On this machine I often
get bit by address space randomization, which means that
addresses for watchpoints aren't consistent across runs
of the inferior.

According to the setarch man page, 'setarch -R' will
disable randomization.  It would be helpful if gdb
implicitly did this same thing at startup.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]