[Bug 1215] New: - wine on FreeBSD: wine in malloc(): error: recursive call

http://bugs.winehq.com/show_bug.cgi?id=1215

           Summary: wine on FreeBSD: wine in malloc(): error: recursive call
           Product: Wine
           Version: 20020904
          Platform: PC
        OS/Version: FreeBSD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: wine-misc
        AssignedTo: wine-bugs(a)winehq.com
        ReportedBy: eta(a)lclark.edu


(Version in use is actually 20021031, but this error has existed for a long
time, on both -current and -stable, from ports or CVS).

After using any windows binary I've tried with FreeBSD's wine from ports, I
eventually get an error:
wine in malloc(): error: recursive call

It also shows up as "wine in free(): error: recursive call," and sometimes
several of them can show up in the output.  The application hangs soon
afterwards (I am guessing it's right when the malloc recursion happens).  In
particular I've been trying to use the Exile 3 binary, but with that it happens
after some minutes of play.  When I was trying counterstrike it happened very
quickly.

Notable excerpt from the malloc manpage:

     recursive call  A process has attempted to call an allocation function
     recursively.  This is not permitted.  In particular, signal handlers
     should not attempt to allocate memory.

However, I think I've tracked down the mallocs/frees that can happen as a result
of signals.  One set (server/registry.c) I patched to not malloc/free.  I put in
a printf around the segv handler, and this recursive malloc doesn't appear to be
happening during segv.  Would the rforking(RFPROC|RFMEM) cause this?

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1215>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.