On Tue, Oct 07, 2003 at 10:26:05PM +0200, André Johansen wrote:
> * Jukka Heinonen wrote:
> | Well, you could try using +relay debugmsg flag
>
> Here are some lines around the crash-point; compare it to the previous
> one (I made sure some output from that one was preset in my cut-out):
>
> $ win
Steven Edwards <[EMAIL PROTECTED]> writes:
> Yes [Un]Map[SL/LS] calls should all be marked as janitorial. They are
> 9x only and we dont want to have to try and implement a hack in
> ReactOS.
You can't get rid of MapSL, it's necessary for 16-bit support; all you
can do is separate the 16-bit code
--- Eric Pouech <[EMAIL PROTECTED]> wrote:
> may be (code janitorial) we could get rid of all MapSL and
> PTR_REAL_TO_LIN calls, and just use the CTX_SEG_OFF_TO_LIN macro
> instead
> ? That would be more readable IMO.
> A+
Yes [Un]Map[SL/LS] calls should all be marked as janitorial. They are
9x
* Jukka Heinonen wrote:
| Well, you could try using +relay debugmsg flag
Here are some lines around the crash-point; compare it to the previous
one (I made sure some output from that one was preset in my cut-out):
$ wine --debugmsg +int,+int31,+relay ./Setup 2> /tmp/trace
>From /tmp/trace:
[...]
On Tue, Oct 07, André Johansen wrote:
> Is it possible to add more trace messages somewhere or get a larger
> call-stack?
Well, you could try using +relay debugmsg flag, but that usually
yields way too large traces. Probably the easiest way would be adding
manually TRACE (or ERR) lines to suspicio
* Jukka Heinonen wrote:
| Unfortunately trace does not
| contain information about where the crash happened but I guess
| since this bug is in the same routine called on the last lines
| of trace (trace:int:MSCDEX_Handler CDROM device driver -> command <128>),
| fixing this bug may help.
Is it pos
On Tue, Oct 07, Eric Pouech wrote:
> may be (code janitorial) we could get rid of all MapSL and
> PTR_REAL_TO_LIN calls, and just use the CTX_SEG_OFF_TO_LIN macro instead
> ? That would be more readable IMO.
Well, that would be a good idea. I was actually planning to
post a patch that would make
Please, if you can, try the patch below and report what happens.
may be (code janitorial) we could get rid of all MapSL and
PTR_REAL_TO_LIN calls, and just use the CTX_SEG_OFF_TO_LIN macro instead
? That would be more readable IMO.
A+
--
Eric Pouech
On Tue, Oct 07, 2003 at 12:29:15AM +0200, André Johansen wrote:
> * Jukka Heinonen wrote:
> | Okay, I have posted a patch to wine-patches that
> | should have fixed this bug. Let's see if that is
> | the case.
>
> Thanks -- I've tested it, and it seems to get further now. It still
> crashes, tho
On Tue, Oct 07, Sylvain Petreolle wrote:
> I still get a crash with WinDVD.
> Attached : trace with +int (int 1a has no other debug channel) and
> disass around $eip.
Well, well. This looks pretty interesting.
It looks like the program is trying to call
PCI BIOS routine "FIND PCI DEVICE" from
32-b
I still get a crash with WinDVD.
Attached : trace with +int (int 1a has no other debug channel) and
disass around $eip.
--- Jukka Heinonen <[EMAIL PROTECTED]> a écrit :
> Okay, I have posted a patch to wine-patches that
> should have fixed this bug. Let's see if that is
> the case.
>
> It may
* Jukka Heinonen wrote:
| Okay, I have posted a patch to wine-patches that
| should have fixed this bug. Let's see if that is
| the case.
Thanks -- I've tested it, and it seems to get further now. It still
crashes, though...
As you can see, it now crashes in another executable.
$ wine ./Setup
Okay, I have posted a patch to wine-patches that
should have fixed this bug. Let's see if that is
the case.
It may be that bug has still not been
fixed by that patch. In that case last lines
of trace "wine --debugmsg +int,+int31" before
the point where application crashes would be helpful.
--
J
* Sylvain Petreolle wrote:
| Please give more inforamtion. (cf
| http://www.winehq.org/site/docs/wine-user/bugs)
wineconfig was happy -- I have two Wine installations; it noticed
that, and some registry notice:
026. Checking availability of windows registry entries... NOTICE (entry "Default
Ta
--- André_Johansen <[EMAIL PROTECTED]> a écrit :
> This crash happens when trying to run the installer of a game; I
> believe it is some old InstallShield version.
>
> Any ideas of how I can get more information out of this?
Please give more inforamtion. (cf
http://www.winehq.org/site/docs/wine
This crash happens when trying to run the installer of a game; I
believe it is some old InstallShield version.
Any ideas of how I can get more information out of this?
The output below is from starting the installer in winedbg:
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINMM.DLL' (0x
16 matches
Mail list logo
