Segmentation Fault

[Kye Lewis]

Hi,

Not really sure if this is the right place to post this, but as i'm
signed up to it;

My version of wine has suddenly started Seg Faulting on startup.

The last thing I tried with wine was netmeeting.

This is with cvs version from 26th October at about 2:00 Australian
Eastern Standard Time ( not sure what that is GMT - it was about 5 hours
before posting this message )

Any help would be appreciated.

Thanks,
Kye Lewis
kyethespy(a)liquid2k.com

[Uwe Bonnes]

> > > > > "Kye" == Kye Lewis <kyethespy(a)liquid2k.com> writes:

Kye> Hi, Not really sure if this is the right place to post this, but as
    Kye> i'm signed up to it;

    Kye> My version of wine has suddenly started Seg Faulting on startup.

The next thing you should try is a littel debugging, like running with relay
messages or starting the application in winedbg or using strace on wine

Bye

-- 
Uwe Bonnes                bon(a)elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. [phone] -------- Fax. [phone] ----------

[Kye Lewis]

On Sat, 2002-10-26 at 22:41, Uwe Bonnes wrote:
> > > > > > "Kye" == Kye Lewis <kyethespy(a)liquid2k.com> writes:
>
> Kye> Hi, Not really sure if this is the right place to post this, but as
>     Kye> i'm signed up to it;
>
> Kye> My version of wine has suddenly started Seg Faulting on startup.
>
> The next thing you should try is a littel debugging, like running with relay
> messages or starting the application in winedbg or using strace on wine

Hi,

Firstly, I need to make sure it's clear that wine is Seg Faulting with
any application I try to run with it

I have tried re-compiling it (the version is the latest CVS), and i've
tried following some of the recomended steps from the FAQomatic @ winehq
- with no success

Winedbg quits with:

No debug information in xxxxxxxxxxxxxx
....
No debug information in xxxxxxxxxxxxxx
Invalid address for breakpoint 1, disabling it
Invalid address for breakpoint 2, disabling it
Process of pid=08444840 has terminated

Any extra command-line options that I should put on winedbg to help find
out the problem?
> Bye
>
> -- 
> Uwe Bonnes                bon(a)elektron.ikp.physik.tu-darmstadt.de
>
> Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
> --------- Tel. [phone] -------- Fax. [phone] ----------

[Kye Lewis]

> Hi,
>
> Firstly, I need to make sure it's clear that wine is Seg Faulting with
> any application I try to run with it
>
> I have tried re-compiling it (the version is the latest CVS), and i've
> tried following some of the recomended steps from the FAQomatic @ winehq
> - with no success
>
> Winedbg quits with:
>
> No debug information in xxxxxxxxxxxxxx
> ....
> No debug information in xxxxxxxxxxxxxx
> Invalid address for breakpoint 1, disabling it
> Invalid address for breakpoint 2, disabling it
> Process of pid=08444840 has terminated
>
> Any extra command-line options that I should put on winedbg to help find
> out the problem?

Just a little more info...

Wine is working with notepad.exe, calc.exe, winhlp32.exe, 
and seemingly fine with console apps like ping.exe (eg. It doesn't
segfault)

Some applications (eg. pbrush.exe, write.exe) don't fault, they just
quit silently back to the bash prompt

But other apps like Acrobat Reader (acrord32.exe) and media player
(mplayer.exe, mplayer2.exe and wmplayer.exe) ARE faulting.

Only the first application in the session to fault says so - the rest
just freeze after the 'See wine User guide...' text, and cannot be
CTRL+C'd out of.

As well, the wine processes in the background cannot be killed with a
killall wine, however wineserver can..

Thanks,
Kye Lewis
kyethspy(a)liquid2k.com

[Eric Pouech]

> Any extra command-line options that I should put on winedbg to help find
> out the problem?
no. it seems however that:
- debug info is not found. Either you did remove -g flags from
compilation, or you have two wine trees (or installation), and lookup
isn't done on the right tree (install)
- your application dies before the debugger did finish its startup. you
could also try to run your app from the debugger (winedbg your_app
instead of wine your_app)

what's strange however, if your wine always crashes at startup, how come
winedbg can actually start up. something's really strange in your
configuration

A+

[Kye Lewis]

>no. it seems however that:
	>- debug info is not found. Either you did remove -g flags from
	>compilation, or you have two wine trees (or installation), and
lookup
	>isn't done on the right tree (install)

Well I definitely haven't removed any flags. My installation was a
straight ./tools/wineinstall.

I've gone through a cleanup to make sure there's no wine left before I
tried re-installing, but it hasn't helped much.

I've tried re-installing 0409, 1007 and the 2610 CVS Version with no
success.

	>- your application dies before the debugger did finish its
startup. 	>you could also try to run your app from the debugger
(winedbg 	>your_app instead of wine your_app)

	>what's strange however, if your wine always crashes at startup,
how 	>come winedbg can actually start up. something's really strange
in 	>your configuration

Well, wine doesn't crash on notepad, so my guess is that it's not
crashing in winelib ported apps - but I'm not 100 percent sure

It seems odd to me that I don't get a segfault on pbrush.exe (it just
silently fails) - I'll try running that with winedbg --debugmsg warn+all
when I go back into linux later on (am in windows right now)

It all seems to have occurred when compiling and installing the 20022610
CVS, so I guess whatever happened may have happened while installing
that.

Thanks,
Kye Lewis
kyethespy(a)liquid2k.com