Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!samsung!umich!terminator!pisa.ifs.umich.edu!rees From: rees@pisa.ifs.umich.edu (Jim Rees) Newsgroups: comp.sys.apollo Subject: Re: dde and tb troubles Message-ID: <4d79e09d.1bc5b@pisa.ifs.umich.edu> Date: 18 Oct 90 19:06:45 GMT References: Sender: usenet@terminator.cc.umich.edu (usenet news) Reply-To: rees@citi.umich.edu (Jim Rees) Organization: University of Michigan IFS Project Lines: 21 In article , hanche@imf.unit.no (Harald Hanche-Olsen) writes: I have here this program that I run on a DN10k, displaying its output via X on a DN3k. I am trying to find out why it crashes. Enter good ole tb: Your program probably isn't leaving a process dump. The reason tb seems to hang is that it's trying to resolve a procedure name given a uid, and the executable file containing that procedure is long gone. Process dumps are kept in \`node_data/system_logs/proc_dump , which you can remove (and reboot) if you want to clear out old tracebacks. Not having tb, I decided to run my program in dde instead. However, then the program never gets to the point were it crashed, because first this program, which uses xgks, causes that package to wait for a mouse press. It's a bad idea to try to run dde on a program that uses an X display on the same screen as dde. That's because dde uses dialog/gpr and interacts badly with X. The way I get around this is to redirect the program I'm trying to debug to a different display on another node. Maybe someday there will be a version of dde that uses X.