This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
tui/1579: GDB should cache the source files for the executable being debugged
- From: agraph03 at yahoo dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 1 Mar 2004 20:46:36 -0000
- Subject: tui/1579: GDB should cache the source files for the executable being debugged
- Reply-to: agraph03 at yahoo dot com
>Number: 1579
>Category: tui
>Synopsis: GDB should cache the source files for the executable being debugged
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon Mar 01 20:48:01 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: agraph03@yahoo.com
>Release: 5.2.1
>Organization:
>Environment:
Linux (non OS specific really)
>Description:
Whenever debugging anything gdb IMNSHO should cache
the source files being debugged so that if you edit the source while debugging an executable that does not
result in a gibberish (text at the wrong offset in the source file) being displayed.
Debuggers for windoze adapted to user editing the source
being debugged for ages. And so should gdb.
339 REQUIRE2(abuff,1);
(gdb) n
340 REQUIRE2(abuff,1);
(gdb) n
341 char c = *abuff();
Here the source was edited.
Then you start to get this.
(gdb)
342 uff();
(gdb)
344 fputc(c, debug);
(gdb)
349 ;
>How-To-Repeat:
Add some code to the source file being shown during debug session, save the file and resume going thru the code.
>Fix:
Load the source file into memory before starting debugging. Modern machines got plenty of ram.
>Release-Note:
>Audit-Trail:
>Unformatted: