Molle Bestefich wrote:
Been running 0.9.15 for a while without problems.
Since a week ago (or so) when I updated to HEAD, all I get from Wine
is this:
wine-git # notepad
Segmentation fault
Nuking ~/.wine doesn't help:
Just to confirm, I get the same problem, segmentation fault when
Christoph Frick wrote:
another good chance to skrew up: when you build your stuff in the same
directory over and over again from cvs/git/nameit and you have change in
your build environment, then even a ``make depend`` wont help you -
autohell does not check against gcc, CFLAGS, ... - make
Been running 0.9.15 for a while without problems.
Since a week ago (or so) when I updated to HEAD, all I get from Wine is this:
wine-git # notepad
Segmentation fault
Nuking ~/.wine doesn't help:
wine-git # rm -rf ~/.wine
wine-git # notepad
wine: creating configuration directory '/root/.wine
Sunday, July 30, 2006, 9:55:57 PM, Molle Bestefich wrote:
Been running 0.9.15 for a while without problems.
Since a week ago (or so) when I updated to HEAD, all I get from Wine is this:
wine-git # notepad
Segmentation fault
[skip]
Any suggestions (please!)?
Yes of course:
Please file
Vitaliy Margolen wrote:
Any suggestions (please!)?
Yes of course:
Please file a proper bug report in Bugzilla. And use wine-users ML for this.
That's hardly very helpful, but thanks anyway.
The only thing I can think of that might have happened (other than a
Wine bug) is GCC or GLIBC being upgraded by 'emerge world'. GCC
--version says gcc (GCC) 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0,
pie-8.7.8), while ls /lib/libc* says libc-2.3.6.so.
Perhaps you can revert to 0.9.15 and rebuild
Hi Mike,
The problem seems to be with the name of the executable:
user.exe (sounds crazy, but it was I could realize after some tests).
That's quite possible. user.exe is a 16 bit part of user32.dll, and
Wine treats it in a special way.
In fact there are a little more with same
However winecfg does not allow me to input free form strings (at least I
try and could not find a way).
It does only allow me to navigate throught the file system and choose the
application.
And the Libraries tab, in winecfg, it is only for DLL's - I guess! (Am I
wrong?)
No, it can be used
Hi all,
I have posted a comment at
http://bugs.winehq.org/show_bug.cgi?id=4351
The problem seems to be with the name of the executable:
user.exe (sounds crazy, but it was I could realize after some tests).
Regards.
-
[EMAIL PROTECTED] wrote:
The problem seems to be with the name of the executable:
user.exe (sounds crazy, but it was I could realize after some tests).
That's quite possible. user.exe is a 16 bit part of user32.dll, and
Wine treats it in a special way.
You might be able to add a
Alex,
Thanks for the reply.
I am going to wait for a pre built (RPM package) for wine-0.9.6
because if I compile I think I can introduce too many variables.
Anyway, I am goig to report your sugestions with wine 0.9.5 and,
ASAP, with wine-0.9.6.
Where can somebody
in order to clean up). If
this is true, then RtlImageNtHeader is violating this rule. Your
segmentation fault might be the expected result of a violation of the
return rule. Could anybody in wine-devel speak up to confirm or refute
this observation about exception handlers?
This, of course, does
Alex,
Exactly the same problem with wine-0.9.6 (pre-built - downloaded
from sourceforge) ..
Wanna trace?
Is there a bug report for this application (bugs.winehq.org)?
Now, you are going to need? I can do it
Have you tried running the installer under winedbg
clause of an
exception handler in Wine (most probably because __ENDTRY needs to run
in order to clean up). If this is true, then RtlImageNtHeader is
violating this rule. Your segmentation fault might be the expected
result of a violation of the return rule. Could anybody in wine-devel
speak up
in Wine
(most probably because __ENDTRY needs to run in order to clean up). If
this is true, then RtlImageNtHeader is violating this rule. Your
segmentation fault might be the expected result of a violation of the
return rule. Could anybody in wine-devel speak up to confirm or refute
(0x7fd8,0002,0012): returning
0x7fd84a08
0009:Ret ntdll.RtlAllocateHeap() retval=7fd84a08 ret=7fce526d
0009:Call ntdll.RtlImageNtHeader() ret=7fce61da
0009: *killed* exit_code=0
Segmentation Fault
- 8 -
I have ARS Remedy versions V3.0
:trace:heap:RtlAllocateHeap (0x7fd8,0002,0012): returning
0x7fd84a08
0009:Ret ntdll.RtlAllocateHeap() retval=7fd84a08 ret=7fce526d
0009:Call ntdll.RtlImageNtHeader() ret=7fce61da
0009: *killed* exit_code=0
Segmentation Fault
- 8 -
I
there( it
basicly only
prevents that you get some useful debug traces, by saving a few instructions)
And like already stated, it used to work in wine too. Until some days ago.
So why shouldn't that reported here?
Just for the record:
I can confirm the segmentation fault(gcc 3.4.4), when compiled
Peter Beutner wrote:
Besides there is nowhere stated that there are only certain supported compiler
flags which
you should use.
Correct. Using any compiler flags other than what configure adds by
default is unsupported, untested and unreliable. Even seemingly
harmless flags such as -Wall
starting just
wine, notepad or anything else, ends up quickly with Segmentation
fault.
this is my simple custom buildscript...
i can confirm this. i use -mtune=athlon-tbird but somewhere after
between 20050930 and CVS-current this error slipped into wine. i can
not easily test against the patch
On Mon, 07 Nov 2005 10:25:17 +0100, Christoph Frick [EMAIL PROTECTED]
wrote:
oh well and btw: gcc 4.0.2.pre (or so) is my compiler.
come on fellas! now you're using unstable , pre-release compilers.
please dont waste time here. There enough true disfunctionality in Wine
that needs to be
On Mon, Nov 07, 2005 at 12:31:37PM +0100, [EMAIL PROTECTED] wrote:
oh well and btw: gcc 4.0.2.pre (or so) is my compiler.
come on fellas! now you're using unstable , pre-release compilers.
please dont waste time here. There enough true disfunctionality in Wine
that needs to be tracked down
On Mon, 07 Nov 2005 14:17:13 +0100, Christoph Frick [EMAIL PROTECTED]
wrote:
something is fishy in
wine and at least its good to talk about it... and prevent this in the
future.
quite so, I think this got sorted pretty quickly by Rob so the patch
should get into cvs to solve the anomoly.
Mike McCormack wrote:
http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are
safe cflags, and it worked until couple days ago, then something is
definetly wrong, right?
This is the wrong type of question for wine-devel, and better asked in
Gentoo forums or wine-users.
why it
zhilla wrote:
why it is wrong? developers are much more likely to know about compiler
flags than users, and gentooers probably use much more bleeding edge
version of gcc anyway
The way developers recommend compiling Wine is explained in the README
file. If you want our help, please try
, including starting just
wine, notepad or anything else, ends up quickly with Segmentation
fault.
this is my simple custom buildscript...
PKGDATE=`date +%Y%m%d`
CHOST=i686-pc-linux-gnu \
CFLAGS=-march=athlon-xp -O2 -pipe -fomit-frame-pointer -m3dnow -msse
-mmmx \
CXXFLAGS=$CFLAGS
On Sun, 06 Nov 2005 19:11:26 +0100, [EMAIL PROTECTED] wrote:
On Sun, 06 Nov 2005 05:29:02 +0100, zhilla [EMAIL PROTECTED] wrote:
before submitting this as bug, some advice please...
well if you have to pretend your Athlon-xp is a 486 to get wine to work
I would say there's a problem that
instructions)
And like already stated, it used to work in wine too. Until some days ago.
So why shouldn't that reported here?
Just for the record:
I can confirm the segmentation fault(gcc 3.4.4), when compiled with
-fomit-frame-pointer.
I will try to find out which patch has caused this.
to WineHQ.
Just for the record:
I can confirm the segmentation fault(gcc 3.4.4), when compiled with
-fomit-frame-pointer.
I will try to find out which patch has caused this.
That would be a great idea.
Mike
.
then why not tell him that?
Besides there is nowhere stated that there are only certain supported compiler
flags which
you should use.
Just for the record:
I can confirm the segmentation fault(gcc 3.4.4), when compiled with
-fomit-frame-pointer.
I will try to find out which patch has caused
quickly with Segmentation
fault.
this is my simple custom buildscript...
PKGDATE=`date +%Y%m%d`
CHOST=i686-pc-linux-gnu \
CFLAGS=-march=athlon-xp -O2 -pipe -fomit-frame-pointer -m3dnow -msse
-mmmx \
CXXFLAGS=$CFLAGS \
./configure \
--disable-debug \
make make depend \
checkinstall -S --pkgname
zhilla [EMAIL PROTECTED] wrote:
then, changed processor optimizations to much more conservative
-O2 -march=i486 -mcpu=i686
and it it works like a charm.
athlon-xp optimizatins used in the first place are from
http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are
safe
zhilla wrote:
http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are
safe cflags, and it worked until couple days ago, then something is
definetly wrong, right?
This is the wrong type of question for wine-devel, and better asked in
Gentoo forums or wine-users.
Mike
Hi,
the current cvs (2005/06/05 14:19:50) gives me a Segmentation Fault on a
simple 'wine' command.
Regression testing is not ended yet, but the problem wasn't there this
morning (with Saturday's CVS).
It appears to be http://cvs.winehq.org/patch.py?id=17949 but I'm not a
100% sure on that one
Paul Vriens wrote:
Hi,
the current cvs (2005/06/05 14:19:50) gives me a Segmentation Fault on a
simple 'wine' command.
I've just updated my tree. Same thing here...
Regression testing is not ended yet, but the problem wasn't there this
morning (with Saturday's CVS).
It appears to be http
Paul Vriens wrote:
It appears to be http://cvs.winehq.org/patch.py?id=17949 but I'm not a
100% sure on that one yet.
Any ideas, or does someone have the same problem ?
I can confirm that patch is the problem, Alexandre will commit a workaround
shortly.
Ivan.
; is
there a more recent release that would build under Solaris?
Thanks,
Mark
On 4/18/05, Mark Greenbank [EMAIL PROTECTED] wrote:
Hi all,
I'm getting a Segmentation Fault when building wine on Solaris 10:
The command itself is:
../tools/winebuild/winebuild -w --def \
-o
Hi all,
I'm getting a Segmentation Fault when building wine on Solaris 10:
The command itself is:
../tools/winebuild/winebuild -w --def \
-o advapi32/advapi32.spec.def --export advapi32/advapi32.spec
gdb stack strace shows:
#0 0xfef229ec in strlen () from /lib/libc.so.1
(gdb
Sorry to reply to my own email; I'm trying to build wine-20050310; is
there a more recent release that would build under Solaris?
Thanks,
Mark
On 4/18/05, Mark Greenbank [EMAIL PROTECTED] wrote:
Hi all,
I'm getting a Segmentation Fault when building wine on Solaris 10:
The command itself
version of wine that I compile, and
.wine from aug, IE6 runs and Help works
3. with wine from September snapshot and .wine from 1013, IE6
creates a segmentation fault
My original symptom was that I couldn't get IE6 Help to work after the
September snapshot
a segmentation fault
My original symptom was that I couldn't get IE6 Help to work after the
September snapshot. I did a regression and identified the commit of
20040824 16:00:16 CDT as causing the problem. The commit edits this patch:
http://cvs.winehq.org/patch.py?id=13475
Among other things this patch
On Tue, 22 Jun 2004 10:32:12 -0700, David Lee wrote:
I am using the CVS wine as of 6/22/04 and when I run the compiled binary
of wine, I get a Segmentation Fault. In fact, most of the wine*
binaries located in /usr/local/bin give me a Segmentation Fault. I have
tried a manual compile
I am using the CVS wine as of 6/22/04 and when I run the compiled binary
of wine, I get a Segmentation Fault. In fact, most of the wine*
binaries located in /usr/local/bin give me a Segmentation Fault. I have
tried a manual compile: ./configure, make depend make, su -c make
install
.
- I tried renaming the files and also creating soft links using
libkernel32.dll.so to kernel32.dll.so.
- If I link like that, my program is giving a 'segmentation fault' error.
- I tried using libraries produced by compiling on my uptodate RH8.0 machine
and also the libraries from the RH8.0 rpm
:
winegcc -o fooapp -loleaut32 fooapp.c
- I implement an XPCOM class using these libraries and when I try to create
an object, it gives the 'Segmentation Fault'.
- I tried using libwine.so but it doesn't contain the above functions I
need.
You should read the WineLib developer guide - you cannot use
There are only few changes between these two days. Maybe this
is enough for someone to find out why this doesn't work on my
system (as others apparently don't have a problem).
For the moment I will stay on the last working version.
Most likely it's the exec shield work around. Make sure you
/bin$ wine -v
wine-20031118
But the following day and later versions I get (as described above):
cvs up -D 2003-11-23 wine
[EMAIL PROTECTED]:/usr/local/bin$ wine -v
Segmentation fault
There are only few changes between these two days. Maybe this
is enough for someone to find out why this doesn't
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
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
Under Windows my program exe file is about 6Mb.
Under Linux and Wine it is about 50Mb (.so file).
It is normal ?
And Wine makes Segmentation fault on initialising global variables of my
program.
#1 0x40bb0116 in __static_initialization_and_destruction_0
(__initialize_p=1, __priority=65535
On Tue, 28 Oct 2003 13:25:53 +0300, Sir flyker scribed thus:
Under Windows my program exe file is about 6Mb.
Under Linux and Wine it is about 50Mb (.so file).
It is normal ?
You probably haven't stripped the binary, so it has full debug symbols in
it. Try using the strip command.
Do you have a line like uxtheme = in your config file ?
I don't have this line in my config file. Should i put it in [DllOverride]
section ?
Stephan
Segmentation fault
This is on Slackware 9.0, Linux 2.6.0-test7.
I had one such line and it was causing the crash for me.
I have found that it is the change in ntdll/loader.c load_dll which
returns NT_STATUS_SUCCESS with a WINE_MODREF** wm set to null.
And then the calling function
Hi folks,
I have a big problem with the last version of wine. I have made 'make
clean', 'make distclean' and recompile everything and i still get a
segmentation fault !
I have deleted all my sources and made a new check out from cvs server.
After running wineinstall, i still get
Hello,
I've updated today from wine and got into troubles after installing it -
got Segmentation fault. I dig in it and figured the problem is my
environment variable WINEDLLPATH which was set to . (current
directory). The back trace of stack during the crash was similar to this
(just
Vincent Béron wrote:
Le mer 10/09/2003 à 11:13, Vincent Béron a écrit :
Le mar 09/09/2003 à 12:34, Juraj Hercek a écrit :
I've fixed the error on my side with
WINEDLLPATH=/usr/local/lib/wine:.. Anyways I think it's a workaround
not a solution... Since I don't know much about
Vincent Béron wrote:
Le mer 10/09/2003 à 11:51, Shachar Shemesh a écrit :
That's exactly the problem I'm having with compiling Wine without
optimizations. the wine binary tries to link with ntdll. ntdll needs
InterlockedCompareExchange from kernel32. In my case, this translates
to a
57 matches
Mail list logo
