I joigned a short list of the calls on the stack. > At a guess it is in glibc or something. Usually > (but not always) a > crash in a library wine uses os because wine calls > it with a bad > parameter or so. > > could you go up the stack a few times until you are > in Wine code and try > "info local"? I'm not easy with winedbg. What should I do to go up the stack ? ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Attachment:
stack_report
Description: stack_report
