[Wine]Wine question - sort of... program that ran now crashes
markknecht at gmail.com
Sun Oct 17 14:58:44 CDT 2004
Duane and James,
I was looking more at this problem and, for now, have decided that
the Gentoo Gods are the root cause of my issues. I spent a bit of time
on the home page for glibc and found that the recommened, current
version is 2.3.3. glibc-2.3.3 works fine for me. It's only 2.3.4 which
fails. I don't know why the Gentoo folks marked a library as stable
when the library maintainers haven't done so, but I really only want
to run the most stable, tested code I can unless there is a security
or performance issue that forces me to move forward more quickly.
I am in the process of taking the machine back to glibc-2.3.3 and
I'm going to stay there for a while.
I want to thank you guys for helping me along the way. I'm going to
spend some more time reading and understanding how to do this
debugging so I'm better prepared in the future.
On Sun, 17 Oct 2004 11:28:21 -0700, Duane Clark <dclark at akamail.com> wrote:
> Mark Knecht wrote:
> > It looks, from the links you pointed me toward, that I'd want to run
> > some form of:
> > $ WINEDEBUG=warn+heap wine program_name
> > However, for me to run Battery as a VST under Wine I do not run Wine
> > directly, but rather I run a program called jack_fst which runs Wine
> > for me. Does this imply that I'd have to change the jack_fst code to
> > call wine in a different way? Of can I set WINEDEBUG in a terminal and
> > then run jack_fst from the same terminal and accomplish the same
> > thing?
> You can just set the environment variable WINEDEBUG. I don't normally
> use the bash shell, but I think the syntax would be:
> WINEDEBUG=warn+heap; export WINEDEBUG
> Normally, to get the output to go to a file, the syntax would then be:
> wine program.exe &> wine.log
> You need that ampersand in there.
> wine-users mailing list
> wine-users at winehq.org
More information about the wine-users