Re: wine_main_preload_info not found, cannot use first megabyte, *.exe don't work

2006-08-02 Thread Pavel Roskin
On Wed, 2006-08-02 at 03:10 +0900, Mike McCormack wrote: David D. Hagood wrote: I've been posting my findings on this very matter to wine-users - look for cannot run under Fedora 6 tset 1. Alexandre has committed a patch that looks like it should fix the problem to the git tree. I

Re: wine_main_preload_info not found, cannot use first megabyte, *.exe don't work

2006-08-01 Thread Mike McCormack
David D. Hagood wrote: I've been posting my findings on this very matter to wine-users - look for cannot run under Fedora 6 tset 1. Alexandre has committed a patch that looks like it should fix the problem to the git tree. Mike

Re: wine_main_preload_info not found, cannot use first megabyte, *.exe don't work

2006-07-31 Thread David D. Hagood
I've been posting my findings on this very matter to wine-users - look for cannot run under Fedora 6 tset 1. I have also found that, if you are running in an SELinux system, you cannot directly run a Windows program using binfmt_misc - the program must have the same security context labels

Re: wine_main_preload_info not found, cannot use first megabyte, *.exe don't work

2006-07-30 Thread Mike McCormack
Pavel Roskin wrote: It is installed and it is run. If I replace wine-preloader with a script that logs the arguments and runs the renamed wine-preloader, I see it being called twice when an exe file with run with Wine. For example: $ wine FarManager170.exe wine_main_preload_info not found

Re: wine_main_preload_info not found, cannot use first megabyte, *.exe don't work

2006-07-30 Thread Pavel Roskin
On Mon, 2006-07-31 at 20:43 +0900, Mike McCormack wrote: OK, it seems to be that the preloader can't lookup the ELF symbol wine_main_preload_info in wine-pthread. I agree. My gdb cannot show variables in 32-bit binaries (or maybe it's just something Wine specific), but it shows the line

Re: wine_main_preload_info not found, cannot use first megabyte, *.exe don't work

2006-07-30 Thread Mike McCormack
Pavel Roskin wrote: I agree. My gdb cannot show variables in 32-bit binaries (or maybe it's just something Wine specific), but it shows the line numbers. I traced find_symbol() in preloader.c, and it seems like symtabend is 0, so that the last loop is skipped and NULL is returned. This is

Re: wine_main_preload_info not found, cannot use first megabyte, *.exe don't work

2006-07-30 Thread Pavel Roskin
Hi Mike, I have found a workaround! On Mon, 2006-07-31 at 00:23 -0400, Pavel Roskin wrote: I agree. My gdb cannot show variables in 32-bit binaries (or maybe it's just something Wine specific), but it shows the line numbers. I traced find_symbol() in preloader.c, and it seems like

Re: wine_main_preload_info not found, cannot use first megabyte, *.exe don't work

2006-07-30 Thread Mike McCormack
Pavel Roskin wrote: find_symbol() looks for DT_HASH (4) to set symtabend and fails to find it. As I understand it, we should trick ld into creating the DT_HASH tag or use some other way to locate wine_main_preload_info. The 6ef5 tag is DT_GNU_HASH - that may be a good alternative to

Re: wine_main_preload_info not found, cannot use first megabyte, *.exe don't work

2006-07-29 Thread Mike McCormack
Pavel Roskin wrote: Something strange to happened my Wine installation recently. I'm getting following messages if I run any program from Wine: $ winemine wine_main_preload_info not found err:dosmem:setup_dos_mem Cannot use first megabyte for DOS address space, please report Looks like

wine_main_preload_info not found, cannot use first megabyte, *.exe don't work

2006-07-28 Thread Pavel Roskin
Hello! Something strange to happened my Wine installation recently. I'm getting following messages if I run any program from Wine: $ winemine wine_main_preload_info not found err:dosmem:setup_dos_mem Cannot use first megabyte for DOS address space, please report wine_main_preload_info not