debugger symbols and NPTL on RedHat 9

Shachar Shemesh wine-devel at
Wed Jun 2 08:49:07 CDT 2004

Hi all,

As mentioned in a previous thread, I'm trying to get a client to migrate 
their product to Linux using Wine. So far, the results have been so so, 
with mightily strange results (sockets in "Established" state with no 
controlling process, zomby processes who's parent is init that are not 
being cleared, etc.). After some looking around, we tried running Wine 
with "LD_ASSUME_KERNEL=2.4.1", and the problems magically disappeared.

Maybe because of the time that passed since these problems were common, 
I clean forgot about this option. I noticed that wine-pthread was 
running instead of wine-kthread, but I did not think of it as a problem 
beyond a theoretical performance problem. It seems, however, that 
guessing wrong had pretty dire side effects.

So, the question <---------------

Will running wine-kthread directly work? Or is there something crucial 
done by the "wine" executable?

Second problem is probably independant. I figured that going through the 
process of getting the program compiled as winelib was unnecessary, so I 
am still compiling it on Windows using Visual Studio. This, naturally, 
means that it's a PE. After resolving the font problems, I can finally 
get the program running through winedbg. While I'm doing ok at working 
like that, the client really prefers working with a GUI. When I try to 
run the program using the --gdb switch (with or without --no-start), 
debug symbols for the PE part are not shown. I get all the symbols for 
the ELF dlls (wine's DLLs), but not for the PE program.

Is this a solveable problem? The program is using PDBs for debug 
symbols, they are not compiled into the PEs. I can change that, I guess, 
but I would really rather not. Will changing that solve anything?


Shachar Shemesh
Lingnu Open Source Consulting

More information about the wine-devel mailing list