WineLib Seg Fault?

lawson_whitney at lawson_whitney at
Mon Nov 19 09:15:33 CST 2001

On Mon, 19 Nov 2001, gerard patel wrote:

> On Mon, 19 Nov 2001 19:35:13 +1100, Jussi Jumppanen
> <jussij at> wrote:
> >A question for the WineLib guru's :)
> >
> >I am using the wine-20011108 build with Mandrake 8.0 and with this
> >version of wine clean compiled and installed I can run several windows
> >programs very successfully :).
> >
> >Then I use winemaker to create a WineLib 'so' file and the compile and
> >link again runs clean.
> >
> >But when I run the resulting 'so' file using this command line:
> >
> >$ WINEPRELOAD=./ wine --debugmsg +all
> >
> >I get the following trace file and resulting segment fault:
> <snip>
> I am no Winelib guru, but why are you running it this way ?
> I was thinking that you have to do a symlink to wine with
> the app name in the app directory. The only occurence
> of WINEPRELOAD I can find in the doc directory is related
> to the debugger.
> Gerard

Do you mean <wine>/documentation?  Surely was there last I
looked.  WINEPRELOAD is alive and well in man wine:

              If set, specifies the full name of a shared library
              that  wine loads and runs as a Winelib application.

That is how I will run the little winelib program that sends this
letter, but calling wine by a symbolic link also works.

Now for _my_ version of "Why are you doing this?":  Why run it with
--debugmsg +all  ??  If you have the source, can you not tell what
functions it is using/interested in/unhappy with the behavior of?
+all spews so much noise it is worthless, and I suspect snoop and relay
traces may interfere with one another in some cases.  For general
debugging, +relay is what you want.


More information about the wine-users mailing list