(none)

Article View: gnu.gdb.bug

Article #10105

#10105

From: pacbell!premenos!phr
Date: Tue, 15 May 1990 01:07

21 lines
1610 bytes

>From premenos.premenos.com!phr Mon May 14 17:47:18 1990
Received:  by premenos.premenos.com (5.59/25-eef)
	id AA02595; Mon, 14 May 90 17:47:18 PDT
Date: Mon, 14 May 90 17:47:18 PDT
From: Paul Rubin <premenos.premenos.com!premenos.premenos.com!phr>
Full-Name: Paul Rubin
Message-Id: <9005150047.AA02595@premenos.premenos.com>
To: pacbell!ames!bug-gdb@prep.ai.mit.edu
Subject: gdb question, suggestion

I hear that there is now a version of gdb that can use the 386 debug
registers to trap when a specified core location is accessed.  Can
someone tell me how to get a copy?

Something I've wanted to see in gdb for a long time is a way of
checkpointing a running process, saving its entire state.  Then I
could take a checkpoint, debug for a while, then back up to where the
checkpoint was.  This could be mostly-implemented in Unix with the
fork system call (checkpointing just makes the debugged process fork
then saves the child process) but might need to be helped by some
simple kernel hacks in GNU.

Technical Details

Message-ID: <9005150107.AA19991@ames.arc.nasa.gov>

Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!snorkelwacker!tut.cis.ohio-state.edu!AMES.ARC.NASA.GOV!pacbell!premenos!phr

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f5053,b42ef22d8d51642a,start
X-Google-Attributes: gidf5053,public
X-Google-ArrivalTime: 1990-05-14 23:07:07 PST
Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!snorkelwacker!tut.cis.ohio-state.edu!AMES.ARC.NASA.GOV!pacbell!premenos!phr
From: pacbell!premenos!phr@AMES.ARC.NASA.GOV
Newsgroups: gnu.gdb.bug
Subject: (none)
Message-ID: <9005150107.AA19991@ames.arc.nasa.gov>
Date: 15 May 90 01:07:21 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 21
Posted: Tue May 15 02:07:21 1990