Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!tarantula.berkeley.edu!shipley
From: shipley@tarantula.berkeley.edu (Pete Shipley)
Newsgroups: comp.windows.x
Subject: Re: Debuggers?
Message-ID: <22946@agate.BERKELEY.EDU>
Date: 12 Apr 89 03:39:18 GMT
References: <2539@scolex.sco.COM>
Sender: usenet@agate.BERKELEY.EDU
Organization: Processed People for a Processed America
Lines: 34

In article <2539@scolex.sco.COM> hiramc@sco.COM (Hiram Clawson) writes:
>Greetings X fans:
>
>I am interested in comments from users of any types of debuggers
>that use an X interface?
>Are such beasts available?
>Pros/Cons - Complaints - Praise - Wish list ?
>If none are now available, are any expected soon from anywhere?
>
>Thanks for your input, significant responses summarized for the net,

on the subject of debuging X here is a X debuging hint:

I have the following code segment in my code:

#ifdef DEBUG
void exit(i)
int i;
{
    (void) fprintf(stderr, "exit code == %d", i);

    /* chdir("/path/to/my/home/dir") */

    abort();
}
#endif DEBUG

This allows me to see the stack after a Xlib or Xt error. since the abort call
will cause a coredump to occur.

Pete Shipley: 
email: shipley@berkeley.edu		Flames:  cimarron@postgres.berkeley.edu 
       uunet!lurnix!shipley or ucbvax!shipley or pyramid!hippo!{ root peter }
Spelling corections: /dev/null                    Quote: "Anger is an energy"