[Wine]A question about debugging apps

[Mark Knecht]

Hi,
   Taking a break for a few minutes from my fst/jack_fst work I
decided to try a quick install of Myst, an old game that has, at
various times, installed, not installed, worked or not worked with
Wine. (According to the app database.) Anyway, I wanted to try it out
so, to cause as few problems as possible for my existing Wine
installation, I created a new user account named myst and then
attempted to install from there, thus creating a new .wine directory,
etc. I su'ed into myst in an xterm, mounted the CD, and then tried
running the installation from the CD. Unfortunately it didn't work.

NOTE: I made no configuration changes to how Wine is running. I just
configured wine by running 'wine notepad' which created directories,
etc., and then tried from there.

   My questions are really about how valid it is to do this.

1) User mark owns the X display. User myst is running Wine. Any
problems? Does user Myst have to log on and start X to run programs
under Wine?

2) When the install died and the debugger started I did a back trace.
I noticed that the debugger is showing /home/mark/CODE/WINE/... which
is probably not a directory that user myst has access to. Is this a
problem? Is this a location the user myst or the debugger needs access
to? Or is it just a name in the code?

myst at flash myst $ cd /mnt/cdrom/
myst at flash cdrom $ ls
archive      channel.dat  install.cfg  mechan.dat  qtw         system.dat
autorun      credits.dat  install.exe  myst.dat    readme.txt
autorun.inf  dunny.dat    intro.dat    myst16      selen.dat
bitmaps      e_reg        making.dat   myst32      stone.dat
myst at flash cdrom $ wine install.exe
wine: Unhandled exception (thread 000d), starting debugger...
WineDbg starting on pid 0xc
Unhandled exception: page fault on read access to 0x77fb0652 in 32-bit
code (0x0046775f).
In 32 bit mode.
Register dump:
 CS:0073 SS:007b DS:007b ES:007b FS:003b GS:0033
 EIP:0046775f ESP:77abfe48 EBP:77abfe9c EFLAGS:00010202(   - 00      - -RI1)
 EAX:004d0000 EBX:77bfe008 ECX:00000040 EDX:77ae064e
 ESI:77fb0652 EDI:00499200
Stack dump:
0x77abfe48:  00465cf7 77eff7c0 77bfe008 00000044
0x77abfe58:  00000000 00000000 00000000 00000000
0x77abfe68:  00000000 00000000 00000000 00000000
0x77abfe78:  00000000 00000000 00000001 00000001
0x77abfe88:  77ae064e 00000008 0000000c 00000010
0x77abfe98:  004d0000 77abff20 00465d69 00465cf7
Backtrace:
=>1 0x0046775f (0x77abfe9c)
  2 0x00465d69 EntryPoint+0x72 in _ins0432._mp (0x77abff20)
  3 0x77b65122 start_process+0xf2(arg=0x0)
[/home/mark/CODE/WINE/wine-20041019/dlls/kernel/process.c:1022] in
kernel32 (0x77abfff4)
  4 0xb7fbd151 wine_switch_to_stack+0x11 in libwine.so.1 (0x00000000)
0x0046775f: repe movsl(%esi),%es:(%edi)
Wine-dbg>bt
Backtrace:
=>1 0x0046775f (0x77abfe9c)
  2 0x00465d69 EntryPoint+0x72 in _ins0432._mp (0x77abff20)
  3 0x77b65122 start_process+0xf2(arg=0x0)
[/home/mark/CODE/WINE/wine-20041019/dlls/kernel/process.c:1022] in
kernel32 (0x77abfff4)
  4 0xb7fbd151 wine_switch_to_stack+0x11 in libwine.so.1 (0x00000000)
Wine-dbg>

I can do more debugging of this, but Myst is not a priority to me. Of
more interest is learning the right way to set this stuff up and to do
the debugging in a proper manner, and then to help solve problems of
interest.

Thanks,
Mark