This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
breakpoints/2213: Darwin: Reloading a program with 'file' seg faults at break point.
- From: nash at nashef dot net
- To: gdb-gnats at sources dot redhat dot com
- Date: 24 Dec 2006 22:38:53 -0000
- Subject: breakpoints/2213: Darwin: Reloading a program with 'file' seg faults at break point.
- Reply-to: nash at nashef dot net
>Number: 2213
>Category: breakpoints
>Synopsis: Darwin: Reloading a program with 'file' seg faults at break point.
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Dec 24 22:48:01 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: nash@nashef.net
>Release: GNU gdb 6.3.50-20050815 (Apple version gdb-573) (Fri Oct 20 15:50:43 GMT 2006)
>Organization:
>Environment:
Apple OS/X (Darwin) 10.4.8
>Description:
I'm iteratively debugging a program in the debugger. If I make a change, recompile, and then load the program again breakpoints cause GDB to drop a Segmentation Fault.
>How-To-Repeat:
Here's a session:
% gdb ./prog
(gdb) list some_function
(gdb) break 55
Breakpoint 1 at 0x2a2e: file prog.c, line 55.
--> Recompile the program here
(gdb) file np
`/path/to/prog' has changed; re-reading symbols.
Breakpoint 1 at 0x2a2e: file prog.c, line 56.
Load new symbol table from "/path/to/program"? (y or n) y
Reading symbols from /path/to/program...done.
(gdb) run --the-args
Starting program: /path/to/program --the-args
Segmentation fault
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: