This is the mail archive of the gdb@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]

Re: GDB Focus Group at the 2008 GCC Summit

From: Nick Roberts <nickrob at snap dot net dot nz>
To: tromey at redhat dot com
Cc: Joel Brobecker <brobecker at adacore dot com>, gdb at sourceware dot org
Date: Tue, 24 Jun 2008 09:55:04 +1200
Subject: Re: GDB Focus Group at the 2008 GCC Summit
References: <20080619190942.GA3744@adacore.com> <18526.15596.855756.886158@kahikatea.snap.net.nz> <m3iqw018r1.fsf@fleche.redhat.com>

 > Nick> Apple GDB already has fix and continue.  Couldn't that be used
 > Nick> as a reference implementaton?
 > 
 > I didn't take notes on this, but apparently fix-and-continue is kind
 > of a pain to implement, and AFAICS needs IDE integration to work
 > properly anyhow.  The Python idea is more of a cute hack than a really
 > serious thing.

I've never really used it but ISTR that Solaris dbx had this feature and there
all you needed to do when excution was stopped, was edit and compile a file,
myfile.c to myfile.o say, then do "fix myfile.o" followed by "continue" and
execution would continue with the new myfile.o patched into the executable.
This all worked from the command line.

-- 
Nick                                           http://www.inet.net.nz/~nickrob

References:
- GDB Focus Group at the 2008 GCC Summit
  - From: Joel Brobecker
- Re: GDB Focus Group at the 2008 GCC Summit
  - From: Nick Roberts
- Re: GDB Focus Group at the 2008 GCC Summit
  - From: Tom Tromey

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