On Fri, 15 Oct 2004, Øyvind Harboe wrote: > > > 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. If this bothers you too much, <http://cygwin.com/acronyms/#PTC>... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] ZZZzz /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing." -- Dr. Jubal Harshaw
