home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky gnu.misc.discuss:4608 comp.sys.hp:15237
- Path: sparky!uunet!elroy.jpl.nasa.gov!sdd.hp.com!saimiri.primate.wisc.edu!tik.vtt.fi!tik.vtt.fi!tml
- From: tml@tik.vtt.fi (Tor Lillqvist)
- Newsgroups: gnu.misc.discuss,comp.sys.hp
- Subject: Re: Attaching gdb to a running process on an HP
- Date: 23 Jan 1993 09:07:14 GMT
- Organization: Technical Research Centre of Finland, Laboratory for Information
- Processing (VTT/TIK)
- Lines: 13
- Message-ID: <TML.93Jan23110713@hemuli.tik.vtt.fi>
- References: <EARL.93Jan22154851@jsi-bwb.jade.ab.ca>
- NNTP-Posting-Host: tik.vtt.fi
- In-reply-to: earl@jade.ab.ca's message of Fri, 22 Jan 1993 22:48:51 GMT
-
- >>>>> On Fri, 22 Jan 1993 22:48:51 GMT, earl@jade.ab.ca (Earl Locken) said:
-
- > We are using gdb 4.6 and gcc 2.2.2 on an HP (yes, I know there
- > are newer versions of gcc, but we are using 2.2.2 for now). Is there
- > any way that we can attach gdb to a running process? Will there ever
- > be a way, or does HP prevent anyone from reading core files?
-
- As HP's debuggers (adb and xdb) can do it, gdb should be able to, if
- only somebody put in the necessary code. It's documented in ptrace(2).
- --
- Tor Lillqvist,
- working, but not speaking, for the Technical Research Centre of Finland,
- Laboratory for Information Processing (VTT/TIK).
-