Re: Crash in 16-bit code

2003-10-11 Thread Jukka Heinonen
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): $ wine

Re: Crash in 16-bit code

2003-10-07 Thread Jukka Heinonen
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-bit

Re: Crash in 16-bit code

2003-10-07 Thread Jukka Heinonen
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, though...

Re: Crash in 16-bit code

2003-10-07 Thread Jukka Heinonen
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

Re: Crash in 16-bit code

2003-10-07 Thread Jukka Heinonen
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

Re: Crash in 16-bit code

2003-10-07 Thread André Johansen
* 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: [...]

Re: Crash in 16-bit code

2003-10-06 Thread Jukka Heinonen
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. --

Re: Crash in 16-bit code

2003-10-06 Thread André Johansen
* 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

Re: Crash in 16-bit code

2003-10-04 Thread Sylvain Petreolle
--- 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

Re: Crash in 16-bit code

2003-10-04 Thread André Johansen
* 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