May 2004 - Wine-Devel - list.winehq.org

Crash due to _fini

by Rajeev Bansal

Hi i am trying to link wine library(msvcrt.dll.so) with my code but i getting segv in _fini call of msvcrt library Please tell me a way so that i can use wine libraries directly without winegcc or specs file on using winegcc for code which contains new and delete operator it gives undefined reference to following symbols operator new(unsigned) operator delete[](void*) _Unwind_Resume __gxx_personality_v0 please help me to resolve above symbols waiting for response Thanks Rajeev Test Program : #include <dlfcn.h> #include <direct.h> #include <math.h> #include <stdio.h> main() { char *a; char *b; double d; void *mod, *ker; const char *error; mod=dlopen("msvcrt.dll.so",RTLD_LAZY); ker=dlopen("kernel32.dll.so",RTLD_LAZY); if(mod) { if ((error = dlerror())) { printf("Couldn't find getcwd: %s\n", error); } if(dlsym(mod, "getcwd")){ printf("found"); b=getcwd(a,20); } dlclose(mod); dlclose(ker); } //end if return (0); } //end main Build command : g++ -g -Wall -c -I/home/timex/wine/wine-20040505/include -I. -I/home/timex/wine/wine-20040505/include/msvcrt test.cpp g++ -g -ldl /home/timex/wine/wine-20040505/dlls/msvcrt.dll.so test.o Debugger output [me(a)cvs TUCP]$ gdb -n GNU gdb Red Hat Linux (5.2.1-4) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux". (gdb) file ./a.out Reading symbols from ./a.out...done. (gdb) break test.cpp:10 Breakpoint 1 at 0x80486cc: file test.cpp, line 10. (gdb) run Starting program: /home/a.out Breakpoint 1, main () at test.cpp:14 14 mod=dlopen("msvcrt.dll.so",RTLD_LAZY); (gdb) next 15 ker=dlopen("kernel32.dll.so",RTLD_LAZY); (gdb) disp mod 1: mod = (void *) 0x40013578 (gdb) disp ker 2: ker = (void *) 0x4026cc40 (gdb) next 16 if(mod) 2: ker = (void *) 0x8049b60 1: mod = (void *) 0x40013578 (gdb) next 19 if(dlsym(mod, "getcwd")) 2: ker = (void *) 0x8049b60 1: mod = (void *) 0x40013578 (gdb) next 20 {printf("found"); 2: ker = (void *) 0x8049b60 1: mod = (void *) 0x40013578 (gdb) next 21 b=getcwd(a,20); 2: ker = (void *) 0x8049b60 1: mod = (void *) 0x40013578 (gdb) step getcwd (buf=0x4026cc40 "T\v\022", size=20) at direct.h:73 73 static inline char* getcwd(char * buf, int size) { return _getcwd(buf, size); } (gdb) step _getcwd (buf=0x4026cc40 "T\v\022", size=20) at dir.c:424 424 int dir_len = GetCurrentDirectoryA(MAX_PATH,dir); Current language: auto; currently c (gdb) step 422 { (gdb) step 424 int dir_len = GetCurrentDirectoryA(MAX_PATH,dir); (gdb) step 422 { (gdb) step 424 int dir_len = GetCurrentDirectoryA(MAX_PATH,dir); (gdb) step Program received signal SIGTRAP, Trace/breakpoint trap. 0x40062179 in _fini () from /home/timex/wine/wine-20040505/dlls/msvcrt.dll.so (gdb) bt #0 0x40062179 in _fini () from /home/timex/wine/wine-20040505/dlls/msvcrt.dll.so #1 0x08048790 in getcwd (buf=0x4026cc40 "T\v\022", size=20) at direct.h:73 #2 0x08048730 in main () at test.cpp:21 #3 0x40161b84 in __libc_start_main () from /lib/libc.so.6 (gdb) --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.642 / Virus Database: 410 - Release Date: 3/24/2004

May 31, 2004

Re: segfault fault at startup

by Mike Hearn

On Mon, 2004-05-31 at 10:59 +0200, Maxime Bellengé wrote: > I also have this segmentation fault. However, when I run > wine-pthread "myprogram", it works perfectly but when I run wine > "myprogram" it hangs. > > So I think the patch to enable exec-shield/preload introduced a > regression. > > Max Can you get a backtrace of the hang please? Attaching to wine with gdb should do the trick. thanks -mike

May 31, 2004

Re: segfault fault at startup

by Maxime Bellengé

I also have this segmentation fault. However, when I run wine-pthread "myprogram", it works perfectly but when I run wine "myprogram" it hangs. So I think the patch to enable exec-shield/preload introduced a regression. Max On Sun, 2004-05-30 at 19:37 +0100, Mike Hearn wrote: > terra(a)gnome.org (Morten Welinder) writes: > > A newly built wine segfaults for me. No args: > > > > welinder(a)anemone:~/wine> ./wine > > Segmentation fault > > > > No core. gdb just reports: > > Try doing an strace and posting the last bits before the segfault > here. > > thanks -mike > > -- Maxime Bellengé <maxime.bellenge(a)laposte.net>

May 31, 2004

Re: segfault fault at startup

by terra＠gnome.org

No change with 'set follow-fork-mode child', or even '... ask'. With strace, I get... strace -i $WINELOADER [...] [40113d71] close(9) = 0 [400f0c37] getpid() = 30133 [40113ce3] open("/tmp/reg75b50000.tmp", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 9 [401140b8] fcntl64(9, F_GETFL) = 0x8001 (flags O_WRONLY|O_LARGEFILE) [40112dcb] fstat64(9, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 [4011e6ed] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40032000 [40121ce7] _llseek(9, 0, [0], SEEK_CUR) = 0 [400b7fdc] --- SIGSEGV (Segmentation fault) @ 0 (0) --- upeek: ptrace(PTRACE_PEEKUSER,30133,48,0): No such process [????????] +++ killed by SIGSEGV +++ Hmm... welinder(a)anemone:~/wine> printenv | grep WINE WINESERVER=/home/welinder/wine/server/wineserver WINELOADER=/home/welinder/wine/loader/wine WINEDLLPATH=/home/welinder/wine/dlls:/home/welinder/wine/programs:/home/welinder/wine/dlls:/home/welinder/wine/programs welinder(a)anemone:~/wine> gdb $WINELOADER GNU gdb 5.3.92 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-suse-linux"... (gdb) tb main Breakpoint 1 at 0x8048857: file glibc.c, line 76. (gdb) r Starting program: /home/welinder/wine/loader/wine [New Thread 16384 (LWP 30150)] [Switching to Thread 16384 (LWP 30150)] main (argc=1, argv=0xbffff414) at glibc.c:76 76 const char *loader = getenv( "WINELOADER" ); (gdb) info symbol 0x400b7fdc nl_langinfo + 60 in section .text (I'm not sure I believe that) Morten

May 31, 2004

Re: Making a system DLL unavailable (problem with COMMCTRL)

by Mike Hearn

On Sat, 29 May 2004 18:20:38 -0400, Samuel Audet wrote: > Is there like a "disable" option in the [DllOverrides] section? Try "commctrl"="native" thanks -mike

May 30, 2004

Re: Help with winedbg

by Eric Pouech

Shachar Shemesh a écrit : > Eric Pouech wrote: > >>> Apparently, there is a problem even without gdb at all. Attached is >>> the output for running "winedbg program", with no arguments at all. >>> >>> The system is a RedHat 9 with kernel 2.4.20-31.9, and the latest >>> glibc available from redhat for it. Wine is CVS tip for today. >>> >>> Shachar >>> err:wineconsole:WINECON_Fatal Couldn't find a decent font, aborting >> >> >> >> <g> it's been a long time we didn't get that one. You don't have fixed >> font installed that matches wineconsole's needs. Usually, it means you >> don't have a fixed font installed. >> >> A+ > > > Hmm..... Is that the reason it can't set the breakpoints???? > > In any case, I'll install fixed fonts on the machine and see where it > leaves me. Do I need to run winedbg through wineconsole? to be precise, the console is created when winedbg launches the child process so that winedbg and the debuggee have too seperate consoles for their output. If setting up wineconsole is an issue, you can: 1/ either remove the CREATE_NEW_CONSOLE flag in winedbg/winedbg.c 2/ fire your executable from the command line, and attaching to it later on. This wouldn't work easily with ddd (still doable, but with pain) you cannot set a bp because since the creation of the console fails, the creation of the debuggee from winedbg fails too. A+

May 30, 2004

Re: segfault fault at startup

by Mike Hearn

terra(a)gnome.org (Morten Welinder) writes: > A newly built wine segfaults for me. No args: > > welinder(a)anemone:~/wine> ./wine > Segmentation fault > > No core. gdb just reports: Try doing an strace and posting the last bits before the segfault here. thanks -mike

May 30, 2004

Re: Help with winedbg

by Shachar Shemesh

Eric Pouech wrote: >> Apparently, there is a problem even without gdb at all. Attached is >> the output for running "winedbg program", with no arguments at all. >> >> The system is a RedHat 9 with kernel 2.4.20-31.9, and the latest >> glibc available from redhat for it. Wine is CVS tip for today. >> >> Shachar >> err:wineconsole:WINECON_Fatal Couldn't find a decent font, aborting > > > <g> it's been a long time we didn't get that one. You don't have fixed > font installed that matches wineconsole's needs. Usually, it means you > don't have a fixed font installed. > > A+ Hmm..... Is that the reason it can't set the breakpoints???? In any case, I'll install fixed fonts on the machine and see where it leaves me. Do I need to run winedbg through wineconsole? Shachar -- Shachar Shemesh Lingnu Open Source Consulting http://www.lingnu.com/

May 30, 2004

Re: Help with winedbg

by Eric Pouech

> Apparently, there is a problem even without gdb at all. Attached is the > output for running "winedbg program", with no arguments at all. > > The system is a RedHat 9 with kernel 2.4.20-31.9, and the latest glibc > available from redhat for it. Wine is CVS tip for today. > > Shachar > err:wineconsole:WINECON_Fatal Couldn't find a decent font, aborting <g> it's been a long time we didn't get that one. You don't have fixed font installed that matches wineconsole's needs. Usually, it means you don't have a fixed font installed. A+

May 30, 2004

Re: segfault fault at startup

by Eric Pouech

Morten Welinder a écrit : > A newly built wine segfaults for me. No args: > > welinder(a)anemone:~/wine> ./wine > Segmentation fault > > No core. gdb just reports: > > welinder(a)anemone:~/wine> LD_LIBRARY_PATH=/home/welinder/wine/libs/wine gdb loader/wine > ... > (gdb) r > Starting program: /home/welinder/wine/loader/wine > [New Thread 16384 (LWP 28622)] > [New Thread 32769 (LWP 28624)] > [New Thread 16386 (LWP 28625)] > Cannot find user-level thread for LWP 28622: generic error > > This is with a suse 9.0 system. > > Ideas? as gdb doesn't by default debug child process and that loader/wine actually passes the real loading phase to loader/wine-[pk]thread depending your setup, you need to tell gdb to debug child process after the fork Use 'set follow-fork-mode child' in gdb for that A+

May 30, 2004