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/reg75b5.tmp", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 9
[40
H!
I have the same Problem.
I get a segfault, when I do "wine myapp" and when I do "wine-pthread"
I'm using a SuSE System ( ~ 9.0 ) with kernel 2.6.6 and gcc 3.4.0
this is the gdb output:
(gdb) set follow-fork-mode child
(gdb) r
Starting program: /usr/local/bin/wine
[New Thread 16384 (LWP 5206)]
[
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.
>
> Ma
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:
> [EMAIL PROTECTED
[EMAIL PROTECTED] (Morten Welinder) writes:
> A newly built wine segfaults for me. No args:
>
> [EMAIL PROTECTED]:~/wine> ./wine
> Segmentation fault
>
> No core. gdb just reports:
Try doing an strace and posting the last bits before the segfault
here.
thanks -mike
Morten Welinder a écrit :
A newly built wine segfaults for me. No args:
[EMAIL PROTECTED]:~/wine> ./wine
Segmentation fault
No core. gdb just reports:
[EMAIL PROTECTED]:~/wine> LD_LIBRARY_PATH=/home/welinder/wine/libs/wine gdb loader/wine
...
(gdb) r
Starting program: /home/welinder/wine/loade
A newly built wine segfaults for me. No args:
[EMAIL PROTECTED]:~/wine> ./wine
Segmentation fault
No core. gdb just reports:
[EMAIL PROTECTED]:~/wine> LD_LIBRARY_PATH=/home/welinder/wine/libs/wine gdb
loader/wine
...
(gdb) r
Starting program: /home/welinder/wine/loader/wine
[New Thread 16
