Nasty Wine/kernel bug, anyone?

[Ulrich Weigand]

Hi Jeremy,

> > Great :-(  Now the interesting thing would be to know *which*
> > semaphore this is waiting on ...
> > 
> > I'd really like to see a kernel stack backtrace on this.  However,
> > there doesn't appear to be an easy way to do so ...
> 
>     I was pretty sure this was going to be a fun one...

OK, I've hacked together a silly tool that generates a
kernel stack backtrace from userspace.

Note that this doesn't do much error checking; please compile
against kernel sources that match the running kernel, and don't
try to use the tool for *running* processes ...

To generate the dump, just run 'dump <pid>'.  The result 
is suitable for piping through 'ksymoops' for symbol lookup.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  weigand at informatik.uni-erlangen.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dump.tar.gz
Type: application/octet-stream
Size: 1252 bytes
Desc: gzip compressed data, deflated, last modified: Mon Mar 26 23:48:50 2001, os: Unix
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20010327/52840f4d/dump.tar.obj