cygwin-xfree Digest 16 Oct 2004 01:22:57 -0000 Issue 1568
Sat Oct 16 08:21:00 GMT 2004
> > > > What can I do to help debug this problem?
> > >
> > > The only way to debug this is to run XWin in gdb and wait until the
> > > error occurs.
> > I've previously built XWin w/debug info and debugged it in GDB.
> > But this time I ran into a new problem:
> > When I run XWin in GDB, it constantly gets access violations. This is
> > during startup, and before I've got some sort of understanding of this,
> > I don't want to attempt anything more ambitious.
> > cygwin1!__getreent
> > KERNEL32!IsBadWritePtr
> This is normal -- this is the way Cygwin (newlib?) tests pointers. Just
> continue from that point. I think there are two or three of those in the
> normal initialization sequence.
After doing this 50 times, it got boring and I gave up.
Last time I debugged XFree86, I didn't have this problem(or maybe once
How many times should I have to endure this requester under normal
Perhaps something is actually wrong?
> If this bothers you too much, <http://cygwin.com/acronyms/#PTC>...
To even debug XFree86 I have to fix a long outstanding complicated
CygWin issue. :-)
More information about the Cygwin-xfree