I'm back at the failing machine now - I'll report back shortly :) rlc
On Sat, Aug 30, 2003 at 04:40:33PM -0400, Christopher Faylor wrote: > On Fri, Aug 29, 2003 at 12:06:28PM -0400, Christopher Faylor wrote: > >On Fri, Aug 29, 2003 at 11:41:52AM +0200, Ronald Landheer-Cieslak wrote: > >>On Thu, Aug 28, 2003 at 10:34:00AM -0400, Christopher Faylor wrote: > >>> On Thu, Aug 28, 2003 at 12:08:20PM +0200, Ronald Landheer-Cieslak wrote: > >>> >With a fresh checkout from cygwin's CVS repo, fresh build, etc. I get this > >>> >when I start rxvt: > >>> > > >>> > 6 [main] rxvt 1912 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION > >>> > 15845 [main] rxvt 1912 open_stackdumpfile: Dumping stack trace to rxvt.exe.sta > >>> >ckdump. > >>> > > >>> >The stackdump is attached. > >>> > >>> Stackdumps of self-built dlls are really not interesting. If you are > >>> building the dll from scratch then you can always debug the problem with > >>> a gdb + working DLL build with --enable-debugging. gdb will show you > >>> exactly where the error is occuring. > >>> > >>> Or you can use addr2line to decode the addresses below: > > ^^ > > ** > >>> > >>$ addr2line -e cygwin1.dll 6107BF59 > >>/home/RLandheer/cygwin/build/i686-pc-cygwin/winsup/cygwin/../../../../src/winsup/cygwin/sync.cc:75 > >> > >>just in case it helps :) > > Any word on this? cygcheck output? Full addr2line decoding of stack > trace? gdb back trace of crash? > > Out of curiousity, has anyone else seen this? > > cgf > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ -- A gambler's biggest thrill is winning a bet. His next biggest thrill is losing a bet. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
