Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-26 Thread Kuba Ober
Thanks Ivan. I did some IRC with Vitaliy, and he came to the conclusion that the outport() code was probably the result of messed up code/stack, since the program doesn't use any hardware or locks. I will look into it tomorrow. As one other possibility, and I'm not trying to suggest that

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-24 Thread Jaap Stolk
On 6/24/06, Vitaliy Margolen [EMAIL PROTECTED] wrote: You can ignore tag altogether. It's only enabled with a special registry key (on windows). And drivers have no way nor need to verify the tag. So I think you can just remove that trace. I will need to think something to stop of from crashing.

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-24 Thread Jaap Stolk
On 6/24/06, Jaap Stolk [EMAIL PROTECTED] wrote: here is the log after remofing the tag altogether: (I had to ctrl-c wine, autocad did not shutdown by itself, so I think things are improving.) $ grep -i ':ntoskrnl:' all_log_no_tag.txt 000f:trace:ntoskrnl:ExAllocatePoolWithTag (1 16 tag),

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-24 Thread Jaap Stolk
found another one :-) I reconstructed the debug output mixed with the wine log: Unhandled exception: page fault on read access to 0x in 32-bit code (0x4062de4e). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:003b GS:0033 EIP:4062de4e

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-24 Thread Jaap Stolk
On 6/24/06, Jaap Stolk [EMAIL PROTECTED] wrote: So the problem is somewhere in load_driver( ). Is there a way to narrow it down a bit more? using objdump I got a bit closer. (note that the exact error address my not be consistent, because I added some more trace functions to the code while

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-24 Thread Vitaliy Margolen
Saturday, June 24, 2006, 3:18:03 PM, Jaap Stolk wrote: On 6/24/06, Jaap Stolk [EMAIL PROTECTED] wrote: So the problem is somewhere in load_driver( ). Is there a way to narrow it down a bit more? using objdump I got a bit closer. (note that the exact error address my not be consistent,

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-24 Thread Jaap Stolk
On 6/25/06, Vitaliy Margolen [EMAIL PROTECTED] wrote: It's pretty hard to see what you doing from this pastes. Do you have time to join one of the Wine's IRC channels? never used that before. I seem to have x-chat. where do i find the correct channel ?

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-24 Thread Vitaliy Margolen
Saturday, June 24, 2006, 4:33:03 PM, Jaap Stolk wrote: On 6/25/06, Vitaliy Margolen [EMAIL PROTECTED] wrote: It's pretty hard to see what you doing from this pastes. Do you have time to join one of the Wine's IRC channels? never used that before. I seem to have x-chat. where do i find the

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-24 Thread Ivan Leo Puoti
Jaap Stolk wrote: from what I could google, code=c096 means that a privileged instruction was found. This is to be expected. DispatchDeviceControl is the function in the driver which handles the IO for the kernel (in this case our fake kernel). If it's a driver it obviously must need to

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-24 Thread Jaap Stolk
On 6/25/06, Ivan Leo Puoti [EMAIL PROTECTED] wrote: Jaap Stolk wrote: from what I could google, code=c096 means that a privileged instruction was found. This is to be expected. DispatchDeviceControl is the function in the driver which handles the IO for the kernel (in this case our fake

Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-23 Thread Jaap Stolk
I'm trying to run Autocad 2004. (installation from cd works) current status: (/blog) http://wiki.jswindle.com/index.php/AutoCad#Forum_Comments It starts a long way, and wine seems to handle the usual CreateFileA(.\\NTICE) and IsDebuggerPresent() properly, and it generates and runs some

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-23 Thread Mike Hearn
On Fri, 23 Jun 2006 14:13:18 +0200, Jaap Stolk wrote: 200145:Backtrace: Hmm seems like you are seeing a mixed debugger/app trace there ... gotta be careful of that!

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-23 Thread Jaap Stolk
I think i found the cause further up in the log. 178591:000f:Starting process Lc:\\windows\\system32\\ntoskrnl.exe ... 178596:wine_dbg_vprintf: debugstr buffer overflow (contents: '000f:trace:ntoskrnl:ExAllocatePoolWithTag (0 20 ') 178597:000f:trace:seh:raise_exception code=8101 flags=1

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-23 Thread Jaap Stolk
ExAllocatePoolWithTag( ) function in the file ntoskrnl_api.c : I changed: WINE_TRACE((%d %ld %.4s), semi-stub\n, PoolType, NumberOfBytes, (char*)Tag); to: WINE_TRACE((%d %ld %4s), semi-stub\n, PoolType, NumberOfBytes, (char*)Tag); Don't know how decimals are supposed to work with a string, but

Re: Autocad 2004 STATUS_INVALID_LDT_OFFSET

2006-06-23 Thread Vitaliy Margolen
Friday, June 23, 2006, 9:47:01 AM, Jaap Stolk wrote: ExAllocatePoolWithTag( ) function in the file ntoskrnl_api.c : I changed: WINE_TRACE((%d %ld %.4s), semi-stub\n, PoolType, NumberOfBytes, (char*)Tag); to: WINE_TRACE((%d %ld %4s), semi-stub\n, PoolType, NumberOfBytes, (char*)Tag);