After updating Linux (glibc) the following problem has surfaced:
[#1] If a Win32 executable is run from the shell with "./pgmname" the program does not run but produces the message "segmentation fault." (If there is a traceback or log then I don't know how to get it.)
[#2] However: if the program is run with "wine ./pgmname" the program runs normally.
Perhaps the most basic problem I have here is that, in scenario #1 when all I get is "segmentation fault," I don't know how to get more info, a traceback or a log.
System is RHLinux 8.0, Wine 20030318, which ran just fine in both scenarios until an update was applied which included glibc.
Incidentally, I rebuilt Wine from source and even rebooted the machine (sigh, thus ending 100-odd days of uptime) with no effect on the prob. Obviously if I knew how to see the real failure-message I could probably shoot it.
"Sundial" == Sundial Services International Inc miker@sundialservices.com writes:
Sundial> After updating Linux (glibc) the following problem has Sundial> surfaced: [#1] If a Win32 executable is run from the shell with Sundial> "./pgmname" the program does not run but produces the message Sundial> "segmentation fault." (If there is a traceback or log then I Sundial> don't know how to get it.)
Sundial> [#2] However: if the program is run with "wine ./pgmname" the Sundial> program runs normally.
Sundial> Perhaps the most basic problem I have here is that, in scenario Sundial> #1 when all I get is "segmentation fault," I don't know how to Sundial> get more info, a traceback or a log.
Sundial> System is RHLinux 8.0, Wine 20030318, which ran just fine in Sundial> both scenarios until an update was applied which included Sundial> glibc.
Sundial> Incidentally, I rebuilt Wine from source and even rebooted the Sundial> machine (sigh, thus ending 100-odd days of uptime) with no Sundial> effect on the prob. Obviously if I knew how to see the real Sundial> failure-message I could probably shoot it.
It seems your kernel is setup ti automatically recognize PE executables. I guess the kernel loader points to some old wine version. Clarify your setup.
Bye