From:	newsham AT lava DOT net (Tim Newsham)
Subject:	Re: concurrency problem (crash) of gnuwin32 b18 in nt 4.0 sp3
13 Feb 1998 23:38:36 -0800 :
Message-ID:	<m0y3QCj-00111tC.cygnus.gnu-win32@malasada.lava.net>
References:	<34E2102C DOT 24EDBA0C AT twain DOT com>
Mime-Version:	1.0
To:	fred AT twain DOT com (Fred T. Hamster)
Cc:	gnu-win32 AT cygnus DOT com

> ( 1000) Stack trace:
> ( 1000) frame 0: sp = 0x241F70C, pc = 0x1000CEC2
> ( 1000) frame 1: sp = 0x241F728, pc = 0x77F94512
> ( 1000) frame 2: sp = 0x241F74C, pc = 0x77F88EEB
> ( 1000) frame 3: sp = 0x241F7D8, pc = 0x77F76266
> ( 1000) frame 4: sp = 0x241F8E4, pc = 0x10020B3A
> ( 1000) frame 5: sp = 0x241F904, pc = 0x1003056B
> ( 1000) frame 6: sp = 0x241F918, pc = 0x1002700B
> ( 1000) frame 7: sp = 0x241F93C, pc = 0x10027070
> ( 1000) frame 8: sp = 0x241F950, pc = 0x10015DD2
> ( 1000) frame 9: sp = 0x241FA30, pc = 0x10024259
> ( 1000) frame 10: sp = 0x241FA3C, pc = 0x1000BBF7
> ( 1000) frame 11: sp = 0x241FF94, pc = 0x1000C113
> ( 1000) frame 12: sp = 0x241FFA0, pc = 0x40F301
> ( 1000) frame 13: sp = 0x241FFB0, pc = 0x40103B
> ( 1000) frame 14: sp = 0x241FFC0, pc = 0x77F1B304
> ( 1000) frame 15: sp = 0x241FFF0, pc = 0x0
> ( 1000) End of stack trace

I have no idea what your problem is, but a hint to get more info:
Compile your binaries with -g.  Run gdb on the binary, set
a breakpoint at main (break main) and start it (run).  Now you
can look at the stack trace and figure out where things are going
wrong:

    list *0x40f301
    list *0x40103b   (<--- these numbers came from the stack trace)
    x/10i 0x100c113
   ... etc ...

you should be able to see the src lines of the calls causing
the problem as well as the names of the library routines called.

                                   Tim N.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -