[Bug 17996] New: inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

Summary: inetmib1 test page faults
           Product: Wine
           Version: 1.1.19
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: testcases
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

[cahrendt@stinky tests]$ make test
../../../tools/runtest -q -P wine -M inetmib1.dll -T ../../.. -p
inetmib1_test.exe.so main.c && touch main.ok

wine: Unhandled page fault on read access to 0x00000000 at address 0x6034fa0d
(thread 005e), starting debugger...
wine client error:5e: read: Bad address
make: *** [main.ok] Error 1

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Vitaliy Margolen   2009-04-10 16:47:53 ---
STOP submitting bogus reports!!! This report does not have ANY information
required.

Distro?
How did you compile Wine?
Did you remove ~/.wine directory and created it before running tests with
winecfg?

And DO NOT file any reports for make test failures!

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #2 from Vitaliy Margolen   2009-04-10 16:48:09 ---
Closing

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #3 from Austin English   2009-04-10 18:10:12 ---
(In reply to comment #1)
> And DO NOT file any reports for make test failures!

Whoa now. Make test failures are still valid bugs (assuming the system is
properly configured).

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #4 from chris ahrendt   2009-04-10 21:37:05 ---
Created an attachment (id=20375)
 --> (http://bugs.winehq.org/attachment.cgi?id=20375)
lshw output

hardware info

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

chris ahrendt  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |UNCONFIRMED
         Resolution|INVALID                     |

--- Comment #5 from chris ahrendt   2009-04-10 21:38:52 ---
This is not an invalid bug... if you look the information is attached..
I am running the latest GIT Tree  and doing tools/wineinstall

then as I stated in another bug report I manually run the test 
as the make test from ~/wine-git fails before getting done.
So I go into each directory and run its test script.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #6 from Vitaliy Margolen   2009-04-11 00:12:47 ---
(In reply to comment #3)
> Make test failures are still valid bugs (assuming the system is
> properly configured).

Exactly. Something tells me this is not valid Wine install/system
configuration.

Chris, first make sure your ~/.wine dir is fresh (remove it, create new,
running winecfg). How did you compile Wine? Attach (as a text file) output of
./configure --enable-maintainer-mode

Run test manually, does it fail by itself? If so, run it under winedbg and
attach complete backtrace at the point it crashes.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #7 from Austin English   2009-04-11 00:53:15 ---
Do you have wine gecko installed?

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #8 from chris ahrendt   2009-04-11 18:45:28 ---
This is a standard GIT  tree install
and is installled via the wineinstall script.

the .wine directory is empty with nothing other than the base configurations.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #9 from chris ahrendt   2009-04-11 19:27:51 ---
Created an attachment (id=20388)
 --> (http://bugs.winehq.org/attachment.cgi?id=20388)
wine config

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #10 from chris ahrendt   2009-04-11 19:28:33 ---
wine gecko is not installed

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #11 from Jeff Zaroyko   2009-04-11 19:31:52 ---
(In reply to comment #8)
> This is a standard GIT  tree install
> and is installled via the wineinstall script.
>
> the .wine directory is empty with nothing other than the base configurations.

so what happens if you run the test manually instead of using make test, can
you attach the terminal output and backtrace?

ps. git is not an acronym, it's written git or Git.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #12 from chris ahrendt   2009-04-11 19:33:00 ---
test is ran manually
same error

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #13 from Jeff Zaroyko   2009-04-11 19:51:08 ---
(In reply to comment #12)
> test is ran manually
> same error

where is the backtrace and terminal output?

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #14 from chris ahrendt   2009-04-11 20:09:09 ---
Manual run command :

../../../tools/runtest -q -P wine -M inetmib1.dll -T ../../.. -p
inetmib1_test.exe.so main.c && touch main.ok

Console Output :

wine: Unhandled page fault on read access to 0x00000000 at address 0x6034fa0d
(thread 0368), starting debugger...
wine client error:368: read: Bad address
make: *** [main.ok] Error 1

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #15 from chris ahrendt   2009-04-11 20:14:44 ---
I do not get a backtrace...

All I get is the above mentioned error...

I will run with winedbug=+inetmib1

Chris

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #16 from chris ahrendt   2009-04-11 20:50:25 ---
Created an attachment (id=20391)
 --> (http://bugs.winehq.org/attachment.cgi?id=20391)
inetmib1 trace file the last 600,000 lines

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #17 from chris ahrendt   2009-04-11 20:51:21 ---
can't put the whole trace up as it is 4 gigs.. so sending only the last 600k
lines of the file.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #20375|application/octet-stream    |text/plain
          mime type|                            |

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #20388|application/octet-stream    |text/plain
          mime type|                            |

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #18 from Vitaliy Margolen   2009-04-12 11:46:00 ---
Where is run under winedbg with valid backtrace?

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #19 from chris ahrendt   2009-04-12 14:24:54 ---
its the trace file I attached...

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #20 from Vitaliy Margolen   2009-04-12 15:09:56 ---
(In reply to comment #19)
> its the trace file I attached...

HUH what? I'm talking about the winedbg program. You run test under it. You
attach backtrace of the crash. Nowhere did I asked for any WINEDEBUG flags!

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #21 from chris ahrendt   2009-04-12 16:18:57 ---
EXPORT WINEDEBUG=+inetmib1 is the flag that was used..
there was no backtrace in winedebug just the exception.
The only thing I got was the trace file that I attached the last
600k lines of.. the original trace was over 4 gigs and I was unable to 
upload it as it was too big even zipped.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #22 from Vitaliy Margolen   2009-04-12 16:53:38 ---
User can't produce required output - invalid.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #23 from Vitaliy Margolen   2009-04-12 16:53:50 ---
Closing

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #24 from Vitaliy Margolen   2009-04-12 16:54:18 ---
If you having difficulties reading English - do not use Bugzilla in the future!

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

chris ahrendt  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |UNCONFIRMED
         Resolution|INVALID                     |

--- Comment #25 from chris ahrendt   2009-04-12 17:57:34 ---
I provided everything requested using the method required..

I have no problem reading or understanding english...

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #26 from Vitaliy Margolen   2009-04-12 18:14:27 ---
(In reply to comment #25)
> I have no problem reading or understanding english...

Then you must be blind.

Nowhere did I asked for WINEDEBUG flags. I explicitly asked to run test under
"winedbg" AGAIN READ THIS >>> "winedbg" <<< this is NOT "WINEDEBUG". See
difference? Or you still oblivious?

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #27 from chris ahrendt   2009-04-12 18:27:17 ---
No Not Blind.. and please keep your attitude in check..

and as I have said before I RAN THE APPLICATION IN
WINEDBG!

THERE IS NO BACKTRACE AT ALL!!

The ONLY THING THAT OCCURS IS THE PAGE FAULT

NO STACK 
NO BACKTRACE 
NOTHING BUT WHAT I HAVE ATTACHED HERE!

Manual run command :

../../../tools/runtest -q -P winedbg -M inetmib1.dll -T ../../.. -p
inetmib1_test.exe.so main.c && touch main.ok

or

../../../tools/runtest -q -P winedbg -M inetmib1.dll -T ../../.. -p
inetmib1_test.exe.so main.c && touch main.ok

Both give the same Console Output :

wine: Unhandled page fault on read access to 0x00000000 at address 0x6034fa0d
(thread 0368), starting debugger...
wine client error:368: read: Bad address
make: *** [main.ok] Error 1

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #28 from Vitaliy Margolen   2009-04-12 18:32:37 ---
You need something like this:
$wine winedbg inetmib1_test.exe.so
WineDbg starting on pid 0017
start_process () at
/usr/local/src/wine.git-build/dlls/kernel32/../../../wine.git/dlls/kernel32/process.c:946
0x7b87859b start_process+0x12b
[/usr/local/src/wine.git-build/dlls/kernel32/../../../wine.git/dlls/kernel32/process.c:946]
in kernel32: movl %esi,0x0(%esp)
946             ExitThread( entry( peb ) );
Wine-dbg>c

<crash>
Wine-dbg>bt

<backtrace>

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #29 from chris ahrendt   2009-04-12 18:37:27 ---
First chance exception: page fault on read access to 0x00000000 in 32-bit code
(0x6034fa0d).
Register dump:
 CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
 EIP:6034fa0d ESP:0033fa70 EBP:0033faa8 EFLAGS:00210206(   - 00      - RIP1)
 EAX:00000001 EBX:60352104 ECX:0000000a EDX:00000000
 ESI:0033fc5c EDI:00000000
Stack dump:
0x0033fa70:  00000000 00000001 00000004 6033adda
0x0033fa80:  6033c7b8 00000001 0033faa8 6033b02b
0x0033fa90:  00000001 0000000e 0000000a 6033c7b8
0x0033faa0:  00000001 0033fbec 0033fda8 60339eb5
0x0033fab0:  0033fba4 0033fbec 0000000a 0033fd94
0x0033fac0:  00000000 602e7ff4 6033b1c9 6033b3bc
Backtrace:
=>0 0x6034fa0d SnmpUtilOidNCmp+0x5d(oid1=0x33fba4, oid2=0x33fbec, count=10)
[/home/cahrendt/wine-git/dlls/snmpapi/main.c:356] in snmpapi (0x0033faa8)
  1 0x60339eb5 testQuery+0x13d5()
[/home/cahrendt/wine-git/dlls/inetmib1/tests/main.c:351] in inetmib1_test
(0x0033fda8)
  2 0x6033a42f func_main+0xff()
[/home/cahrendt/wine-git/dlls/inetmib1/tests/main.c:476] in inetmib1_test
(0x0033fde8)
  3 0x6033a6c0 run_test+0x130(name="main")
[/home/cahrendt/wine-git/dlls/inetmib1/tests/../../../include/wine/test.h:456]
in inetmib1_test (0x0033fe28)
  4 0x6033a8ae main+0x11e(argc=<register ECX not in topmost frame>,
argv=<register ECX not in topmost frame>)
[/home/cahrendt/wine-git/dlls/inetmib1/tests/../../../include/wine/test.h:505]
in inetmib1_test (0x0033fed8)
  5 0x6033b0c4 __wine_spec_exe_entry+0x84(peb=0x7ffdf000)
[/home/cahrendt/wine-git/dlls/winecrt0/exe_entry.c:36] in inetmib1_test
(0x0033ff08)
  6 0x7b8755b0 start_process+0x130(arg=(nil))
[/home/cahrendt/wine-git/dlls/kernel32/process.c:946] in kernel32 (0x0033ffe8)
0x6034fa0d SnmpUtilOidNCmp+0x5d
[/home/cahrendt/wine-git/dlls/snmpapi/main.c:356] in snmpapi: cmpl     
%eax,0x0(%edi)
356             if (oid1->ids[i] > oid2->ids[i]) return 1;
Wine-dbg>First chance exception: page fault on read access to 0x00000000 in
32-bit code (0x6034fa0d).
Register dump:
 CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
 EIP:6034fa0d ESP:0033fa70 EBP:0033faa8 EFLAGS:00210206(   - 00      - RIP1)
 EAX:00000001 EBX:60352104 ECX:0000000a EDX:00000000
 ESI:0033fc5c EDI:00000000
Stack dump:
0x0033fa70:  00000000 00000001 00000004 6033adda
0x0033fa80:  6033c7b8 00000001 0033faa8 6033b02b
0x0033fa90:  00000001 0000000e 0000000a 6033c7b8
0x0033faa0:  00000001 0033fbec 0033fda8 60339eb5
0x0033fab0:  0033fba4 0033fbec 0000000a 0033fd94
0x0033fac0:  00000000 602e7ff4 6033b1c9 6033b3bc
Backtrace:
=>0 0x6034fa0d SnmpUtilOidNCmp+0x5d(oid1=0x33fba4, oid2=0x33fbec, count=10)
[/home/cahrendt/wine-git/dlls/snmpapi/main.c:356] in snmpapi (0x0033faa8)
  1 0x60339eb5 testQuery+0x13d5()
[/home/cahrendt/wine-git/dlls/inetmib1/tests/main.c:351] in inetmib1_test
(0x0033fda8)
  2 0x6033a42f func_main+0xff()
[/home/cahrendt/wine-git/dlls/inetmib1/tests/main.c:476] in inetmib1_test
(0x0033fde8)
  3 0x6033a6c0 run_test+0x130(name="main")
[/home/cahrendt/wine-git/dlls/inetmib1/tests/../../../include/wine/test.h:456]
in inetmib1_test (0x0033fe28)
  4 0x6033a8ae main+0x11e(argc=<register ECX not in topmost frame>,
argv=<register ECX not in topmost frame>)
[/home/cahrendt/wine-git/dlls/inetmib1/tests/../../../include/wine/test.h:505]
in inetmib1_test (0x0033fed8)
  5 0x6033b0c4 __wine_spec_exe_entry+0x84(peb=0x7ffdf000)
[/home/cahrendt/wine-git/dlls/winecrt0/exe_entry.c:36] in inetmib1_test
(0x0033ff08)
  6 0x7b8755b0 start_process+0x130(arg=(nil))
[/home/cahrendt/wine-git/dlls/kernel32/process.c:946] in kernel32 (0x0033ffe8)
0x6034fa0d SnmpUtilOidNCmp+0x5d
[/home/cahrendt/wine-git/dlls/snmpapi/main.c:356] in snmpapi: cmpl     
%eax,0x0(%edi)
356             if (oid1->ids[i] > oid2->ids[i]) return 1;
Wine-dbg>First chance exception: page fault on read access to 0x00000000 in
32-bit code (0x6034fa0d).
Register dump:
 CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
 EIP:6034fa0d ESP:0033fa70 EBP:0033faa8 EFLAGS:00210206(   - 00      - RIP1)
 EAX:00000001 EBX:60352104 ECX:0000000a EDX:00000000
 ESI:0033fc5c EDI:00000000
Stack dump:
0x0033fa70:  00000000 00000001 00000004 6033adda
0x0033fa80:  6033c7b8 00000001 0033faa8 6033b02b
0x0033fa90:  00000001 0000000e 0000000a 6033c7b8
0x0033faa0:  00000001 0033fbec 0033fda8 60339eb5
0x0033fab0:  0033fba4 0033fbec 0000000a 0033fd94
0x0033fac0:  00000000 602e7ff4 6033b1c9 6033b3bc
Backtrace:
=>0 0x6034fa0d SnmpUtilOidNCmp+0x5d(oid1=0x33fba4, oid2=0x33fbec, count=10)
[/home/cahrendt/wine-git/dlls/snmpapi/main.c:356] in snmpapi (0x0033faa8)
  1 0x60339eb5 testQuery+0x13d5()
[/home/cahrendt/wine-git/dlls/inetmib1/tests/main.c:351] in inetmib1_test
(0x0033fda8)
  2 0x6033a42f func_main+0xff()
[/home/cahrendt/wine-git/dlls/inetmib1/tests/main.c:476] in inetmib1_test
(0x0033fde8)
  3 0x6033a6c0 run_test+0x130(name="main")
[/home/cahrendt/wine-git/dlls/inetmib1/tests/../../../include/wine/test.h:456]
in inetmib1_test (0x0033fe28)
  4 0x6033a8ae main+0x11e(argc=<register ECX not in topmost frame>,
argv=<register ECX not in topmost frame>)
[/home/cahrendt/wine-git/dlls/inetmib1/tests/../../../include/wine/test.h:505]
in inetmib1_test (0x0033fed8)
  5 0x6033b0c4 __wine_spec_exe_entry+0x84(peb=0x7ffdf000)
[/home/cahrendt/wine-git/dlls/winecrt0/exe_entry.c:36] in inetmib1_test
(0x0033ff08)
  6 0x7b8755b0 start_process+0x130(arg=(nil))
[/home/cahrendt/wine-git/dlls/kernel32/process.c:946] in kernel32 (0x0033ffe8)
0x6034fa0d SnmpUtilOidNCmp+0x5d
[/home/cahrendt/wine-git/dlls/snmpapi/main.c:356] in snmpapi: cmpl     
%eax,0x0(%edi)
356             if (oid1->ids[i] > oid2->ids[i]) return 1;

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #30 from Juan Lang   2009-04-13 11:01:35 ---
> From the look of it, one of the oids (vars or vars2) has become corrupt.

There's a NULL-pointer violation:

First chance exception: page fault on read access to 0x00000000 in 32-bit code
(0x6034fa0d).

The debugger shows which variables are being addressed:

356             if (oid1->ids[i] > oid2->ids[i]) return 1;

That is, one of oid1, oid2, oid1->ids, or oid2->ids is NULL.  Looking at the
call stack, we can rule out the first two possibilities:

=>0 0x6034fa0d SnmpUtilOidNCmp+0x5d(oid1=0x33fba4, oid2=0x33fbec, count=10)
[/home/cahrendt/wine-git/dlls/snmpapi/main.c:356] in snmpapi (0x0033faa8)
  1 0x60339eb5 testQuery+0x13d5()

That is, oid1 and oid2 aren't NULL.  So oid1->ids is NULL or oid2->ids is NULL.
 Looking at SnmpUtilOidNCmp some more, they will only be dereferenced if
oids1->idLength is positive, oid2->idLength is positive, and count is positive:

len = min(count, oid1->idLength);
    len = min(len, oid2->idLength);
    for (i = 0; i < len; i++)
    {
        if (oid1->ids[i] > oid2->ids[i]) return 1;

We already know count is 10, from the backtrace.  So both oid1->idLength and
oid2->idLength are positive, but one of oid1->ids or oid2->ids is NULL.  This
is certainly possible, if a memory allocation in SnmpUtilOidAppend fails:  it
will return a failure code, but not reset idLength to 0 if memory allocation
fails.

Without being able to reproduce it here, it's hard to know what's going on. 
Improving the traces to snmpapi might yield a clue.  For example, rather than
tracing the pointer arguments to SnmpUtilOidAppend, the values (ids and
idLength) of the pointers might be traced instead.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #31 from chris ahrendt   2009-04-13 11:06:07 ---
without me touching the inside code what can I do to help with this..
I can't touch the inner wine code...

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #32 from Austin English   2009-04-13 11:50:53 ---
(In reply to comment #31)
> without me touching the inside code what can I do to help with this..
> I can't touch the inner wine code...

Try improving the tracing to debug it, as Juan suggested.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #33 from chris ahrendt   2009-04-14 17:49:51 ---
Created an attachment (id=20454)
 --> (http://bugs.winehq.org/attachment.cgi?id=20454)
here is the snmpapi.out file for the same problem...

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #34 from chris ahrendt   2009-04-23 22:54:22 ---
Still occuring with the latest GIT tree... same

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #35 from Juan Lang   2009-05-01 11:01:45 ---
*** Bug 18306 has been marked as a duplicate of this bug. ***

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #36 from Juan Lang   2009-05-01 11:05:34 ---
Created an attachment (id=20856)
 --> (http://bugs.winehq.org/attachment.cgi?id=20856)
Debug patch

Please apply this patch and run with WINEDEBUG=+snmpapi , and attach the log
file here.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

Juan Lang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
           Keywords|                            |testcase

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #37 from chris ahrendt   2009-05-01 23:43:57 ---
Will try and recreate over the weekend if I get a chance

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #38 from chris ahrendt   2009-05-02 21:25:14 ---
here is the TAIL of the file:

[cahrendt@stinky tests]$ tail ~/testout.txt
trace:snmpapi:SnmpUtilOidCpy (0x32fba4 (14, 0x72fdffb8), 0x32f9fc (9,
0x601ef6c0))
trace:snmpapi:SnmpUtilOidAppend (0x32fba4 (14, (nil)), 0x32f974 (1, 0x32f97c))
trace:snmpapi:SnmpUtilOidAppend (0x32fba4 (14, (nil)), 0x32f9b0 (1, 0x32f9b8))
trace:snmpapi:SnmpUtilOidAppend (0x32fba4 (14, (nil)), 0x32f9b0 (1, 0x32f9b8))
trace:snmpapi:SnmpUtilOidAppend (0x32fba4 (14, (nil)), 0x32f9b0 (1, 0x32f9b8))
trace:snmpapi:SnmpUtilOidAppend (0x32fba4 (14, (nil)), 0x32f9b0 (1, 0x32f9b8))
trace:snmpapi:SnmpUtilOidNCmp (0x32fba4 (14, (nil)), 0x32fbec (10, 0x32fc5c),
10)
wine: Unhandled page fault on read access to 0x00000000 at address 0x601d6a7b
(thread 0009), starting debugger...
wine client error:9: read: Bad address
make: *** [main.ok] Error 1

I can't give you the whole file as its 48 Gig. Is this enough?

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #39 from Juan Lang   2009-05-02 23:17:13 ---
(In reply to comment #38)
> I can't give you the whole file as its 48 Gig. Is this enough?

It's enough.  Wow, 48 Gig.  I couldn't have gathered that even if I wanted to. 
Thanks.
> trace:snmpapi:SnmpUtilOidCpy (0x32fba4 (14, 0x72fdffb8), 0x32f9fc (9,
> 0x601ef6c0))
> trace:snmpapi:SnmpUtilOidAppend (0x32fba4 (14, (nil)), 0x32f974 (1, 0x32f97c))

This shows the problem:  memory allocation must have failed in SnmpUtilOidCpy. 
Immediately after it, SnmpUtilOidAppend has an invalid AsnObjectIdentifier
argument:  its idLength is nonzero, but its ids is NULL.

Probably the test should fail if memory allocation fails.  I'm not sure why
memory allocation is failing in your case.  The fact that the log is so
enormous suggests that:
1) There's a memory leak.
2) There's an unterminated loop.
Problem 2) may be due to some difference in configuration on your system or on
Fedora Core 10 systems than my machines, as I'm not able to reproduce the
problem myself.

Nevertheless, I'll have a look.  It's too late for me to cook up any patches
tonight, so I'll try to have a look within the next couple days.  Thanks for
the help!

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #40 from chris ahrendt   2009-05-02 23:21:43 ---
Anytime Juan
If you need any other trace's let me know and I will run them...
I can recreate this pretty consistently now.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #41 from Juan Lang   2009-05-04 13:10:13 ---
> Probably the test should fail if memory allocation fails.  I'm not sure why
> memory allocation is failing in your case.  The fact that the log is so
> enormous suggests that:
> - There's a memory leak.

Well, I ran the tests under valgrind, and it doesn't report any leak.  So I'm
not sure I can do a lot.  I can add a check whether memory allocation fails to
the tests, but that won't address why it fails in the first place.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #42 from Juan Lang   2009-05-04 13:16:19 ---
Created an attachment (id=20902)
 --> (http://bugs.winehq.org/attachment.cgi?id=20902)
Patch

Does this patch help?

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #43 from chris ahrendt   2009-05-04 17:49:47 ---
nope same exception.

I guess we should test that the memory allocation fails.

If you could tell me how to run under valgrind I could run it on my machine and
see what it says.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #44 from Austin English   2009-05-04 18:07:30 ---
(In reply to comment #43)
> nope same exception.
>
> I guess we should test that the memory allocation fails.
>
> If you could tell me how to run under valgrind I could run it on my machine and
> see what it says.

http://wiki.winehq.org/Wine_and_Valgrind

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #45 from chris ahrendt   2009-05-04 18:37:16 ---
Created an attachment (id=20911)
 --> (http://bugs.winehq.org/attachment.cgi?id=20911)
valgrind run

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #46 from chris ahrendt   2009-05-04 18:40:30 ---
This was done with the following :

valgrind --tool=memcheck --trace-children=yes --leak-check=full wine
inetmib1_test.exe.so

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #47 from chris ahrendt   2009-05-04 18:52:54 ---
The first was a basic valgrind run..  
I am running valgrind now  with all of the flags =D

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #48 from chris ahrendt   2009-05-04 19:35:10 ---
Created an attachment (id=20912)
 --> (http://bugs.winehq.org/attachment.cgi?id=20912)
Valgrnd 2 run

This run was done with the following :

valgrind --tool=memcheck --leak-check=full --show-reachable=yes
--trace-children=yes wine inetmib1_test.exe.so &>~/valgrnd2.txt

Not sure what I am looking at but hope this helps.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #49 from Juan Lang   2009-05-04 22:53:55 ---
Well, your valgrind run doesn't show a memory leak either, so I was wrong about
that part.  I have a handful of patches in inetmib1 that'll make it respect
errors from snmpapi.  With any luck they'll at least create some test failures
before the crash to help narrow it down a little.  Posting them in a sec.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #50 from Juan Lang   2009-05-04 22:55:06 ---
Created an attachment (id=20914)
 --> (http://bugs.winehq.org/attachment.cgi?id=20914)
Patch 1/3

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #51 from Juan Lang   2009-05-04 22:56:17 ---
Created an attachment (id=20915)
 --> (http://bugs.winehq.org/attachment.cgi?id=20915)
Patch 2/3

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #52 from Juan Lang   2009-05-04 22:57:25 ---
Created an attachment (id=20916)
 --> (http://bugs.winehq.org/attachment.cgi?id=20916)
Patch 3/3

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #53 from chris ahrendt   2009-05-05 22:31:37 ---
Just got this.. too late to try patches.. will do tomorrow when I have some
time

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #54 from chris ahrendt   2009-05-06 22:07:48 ---
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.129.36.0.0
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.129.36.0.0,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.129.39.0.0
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.129.39.0.0,
0x32fa98)
main.c:343: Test failed: SnmpExtensionQuery failed: -559038737
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:DllMain (0x0x60360000, 0, (nil))
make: *** [main.ok] Error 1

Thats the Tail of the file... original output file is 3 gig... if you need I
can zip and put it up

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #55 from Juan Lang   2009-05-07 11:41:55 ---
(In reply to comment #54)
> main.c:343: Test failed: SnmpExtensionQuery failed: -559038737

Well, a test failure is better than a crash.  I'll send those in for now, then
think a bit more about where the problem's coming from.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #56 from Juan Lang   2009-05-07 11:53:16 ---
Created an attachment (id=20956)
 --> (http://bugs.winehq.org/attachment.cgi?id=20956)
iphlpapi trace patch

Could you also apply this patch and post a +iphlpapi trace?  I'm curious if
your route table is huge (unlikely), or if there's just a bug enumerating the
table.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #57 from chris ahrendt   2009-05-07 12:42:00 ---
Created an attachment (id=20958)
 --> (http://bugs.winehq.org/attachment.cgi?id=20958)
this is the output of just the iphlp test run

This is the output from just the iphlp test run....
Am running the inetmib1 test now with the iphlp debug turned on... will post
that
when its done

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #58 from Juan Lang   2009-05-07 12:46:15 ---
(In reply to comment #57)
> Created an attachment (id=20958)

--> (http://bugs.winehq.org/attachment.cgi?id=20958) [details]
> this is the output of just the iphlp test run

Thanks, Chris.  This is what I was after:
trace:iphlpapi:AllocateAndGetIpForwardTableFromStack returning ret 0 table
0x113d20 (93 entries)

That's pretty normal.  It's a bit larger than I'd expect, my route table has
only 3 entries, but it's not so massive as to be the culprit.  So there must be
a bug in how entries are searched in the table.  Hm..
> Am running the inetmib1 test now with the iphlp debug turned on... will post
> that when its done

Thanks.  The one you've posted is fine.  Thanks for being willing to apply and
test so many patches!

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #59 from chris ahrendt   2009-05-07 13:53:57 ---
Its the only way it can get fixed since I can't touch the code.. (as you know I
am a contaminated resource so all I can do is test and write test cases =D )
Besides I enjoy doing this

Chris

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #60 from Juan Lang   2009-05-07 14:10:26 ---
(In reply to comment #58)
> So there must be a bug in how entries are searched in the table.  Hm..

I think I'm onto the problem:  if more than one entry in the forward table
shares the same numerical destination address, the function to find the entry
in the table will always find the first entry.  This results in an infinite
loop in enumerating the table.  This, combined with a memory leak, causes the
test to fail on your machine.

I have a patch for the memory leak, but not for the loop.

Having two entries with the same address is not an invalid configuration, as
the entries should be disambiguated by some other field, such as the next hop. 
The current code doesn't allow that to happen.  I need to test more on Windows
what's happening, but I don't have access to a Windows machine at the moment,
so I won't have a fix soon.

Here's what I think is happening:

When enumerating the addresses, the SnmpExtensionQuery function starts with a
base oid, finds the next matching oid, then appends enough information to
identify it so the subsequent query will find the subsequent oid.  The ip
forward table identifies entries by the destination IP address.

So, for example, let's assume that the IP forward table has two entries, with
destination addresses 0.0.0.0 and 0.0.0.1.  Assume the first query is for
1.3.6.1.2.1.4.21.1, the MIB 2 ipForwardTable oid.  The code finds the first
entry in the ipForwardTable, and appends the IP destination address oid (.1)
and IP address of the row to it, so it returns 1.3.6.1.2.1.4.21.1.1.0.0.0.0 as
the oid.  On the subsequent run, it finds the next matching oid after this,
which is the address 0.0.0.1, so it returns 1.3.6.1.2.1.4.21.1.1.0.0.0.1.  On
the subsequent run, no IP addresses match, so mip2IpRouteQuery returns
SNMP_ERRORSTATUS_NOSUCHNAME, and SnmpExtensionQuery goes looking for another
part the MIB 2 table that matches.

Now assume there are only two entries in the route table.  Both of them share
the same destination address, a.  They have different next hop addresses, g1
and g2.  The rest of the entries are the same.  So the table looks like this:
Destination address    Next hop
a                      g1
a                      g2

When called with 1.3.6.1.2.1.4.21.1, SnmpExtensionQuery will return the oid of
the first entry, 1.3.6.1.2.1.4.21.1.1.a.  When called with this a second time,
it'll match the first entry in the table (a/g1), and return the subsequent
entry, for (a/g2), but it'll return the oid 1.3.6.1.2.1.4.21.1.1.a.  When
called a third time, it'll match the first entry, as it only has enough
information to match the destination address, and can't distinguish the first
entry from the second.

I believe what needs to happen is that more information needs to be included in
the oid of an ip route table entry, such as the next hop address.  From RFC
1354, the index of an ipForwardEntry is:
             INDEX {
                 ipForwardDest,
                 ipForwardProto,
                 ipForwardPolicy,
                 ipForwardNextHop
                 }
That is, the destination address, protocol, policy, and next hop should all be
considered the index into the table.  I need to check on Windows whether it
includes all of these in the oid corresponding to a route table entry before
changing anything.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #61 from chris ahrendt   2009-05-07 14:15:44 ---
Anything I could do to help for you? I have several windows machines.. both
vmware as well as a physical one in my home office I use for a file server.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #62 from Juan Lang   2009-05-07 14:34:31 ---
(In reply to comment #60)
> I need to check on Windows whether it includes all of these in the oid
> corresponding to a route table entry before changing anything.

Oops, my tests already indicate that it doesn't:
                /* The base OID for the route table, 1.3.6.1.2.1.4.21.1.1, is
                 * appended with the dest IP address of the entry.  So e.g. a
                 * route entry for 224.0.0.0 is identified in MIB2 as
                 * 1.3.6.1.2.1.4.21.1.1.224.0.0.0
                 */
I don't know what Windows does in the case of ambiguous IP addresses.  Like I
said, more tests needed.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #63 from Juan Lang   2009-05-07 14:53:41 ---
(In reply to comment #61)
> Anything I could do to help for you? I have several windows machines.. both
> vmware as well as a physical one in my home office I use for a file server.

Well, it depends on whether my hunch is correct, and whether one of your
Windows machines has the same condition (duplicate address in the route table)
as the FC10 machine that's currently failing for you.

Just to verify my hunch, I've got a little python script for you to run, if you
don't mind.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #64 from Juan Lang   2009-05-07 14:56:05 ---
Created an attachment (id=20961)
 --> (http://bugs.winehq.org/attachment.cgi?id=20961)
Duplicate address checking script

Chris, would you mind running this and posting the result?  I wrote this rather
than asking you to post your route table, as that would reveal more than you
should probably reveal on the 'net ;-)

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #65 from chris ahrendt   2009-05-07 15:54:15 ---
Yeah I would prefer not to put my route table for all to see.. and you know
why.. lol!

here is the output:

Duplicate address found in route table

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #66 from Juan Lang   2009-05-07 16:01:35 ---
(In reply to comment #65)
> Duplicate address found in route table

Thanks, that confirms my hunch.  Now I need to test a similar condition on
Windows, and see how inetmib1 behaves there under that condition.  I think my
hints are explicit enough that someone else could work on this, otherwise I'll
get to it when I can get some quality time in front of a Windows box.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #67 from chris ahrendt   2009-05-07 16:06:19 ---
If they need me to test fixes or run a debug script let me know... thats the
extent of what I am allowed to do...

One thing that might put dupes in the table could be VPN software but I am not
sure...  let me quickly test a theory....

Ok the VPN is not the answer.. so its something else ...

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #68 from Austin English   2009-05-07 16:10:43 ---
(In reply to comment #67)
> If they need me to test fixes or run a debug script let me know... thats the
> extent of what I am allowed to do...

I'm pretty sure you can contribute test cases...

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #69 from Juan Lang   2009-05-07 17:10:31 ---
(In reply to comment #67)
> One thing that might put dupes in the table could be VPN software but I am not
> sure...  let me quickly test a theory....

Don't worry about that, it's not a problem with your config.  It's just how
your system is configured.  For example, you could have one entry for
10.0.0.0/8 and another for 10.0.0.0/16, with different gateways.  It would be
potentially confusing, but not incorrect.  But the inetmib1 code is buggy in
this situation.

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #70 from Austin English   2009-05-10 03:28:11 ---
*** Bug 17859 has been marked as a duplicate of this bug. ***

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #71 from chris ahrendt   2009-05-10 09:53:52 ---
Juan,
could the duplicates in the route table also be causing the two failures I am
seeing in urlmon tests?

http://test.winehq.org/data/00160719d31aa59b37c358af16c3dabaa04bfd5b/wine_ca...

url.c:2250: Test failed: unexpected OnProgress_FINDINGRESOURCE
url.c:2418: Test failed: unexpected Obj_OnProgress_FINDINGRESOURCE
trace:urlmon:URLMoniker_Release (0x1340e0) ref=2
url.c:2449: Test failed: mon should be destroyed here
trace:ole:BindCtxImpl_Release (0x1385f0)
url.c:2454: Test failed: bctx should be destroyed here

all the Release function is a macro (no way to put tracing on that)

[Bug 17996] inetmib1 test page faults

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #72 from Juan Lang   2009-05-10 17:24:19 ---
(In reply to comment #71)
> could the duplicates in the route table also be causing the two failures I am
> seeing in urlmon tests?

I doubt it.

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

Juan Lang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
            Summary|inetmib1 test page faults   |inetmib1 test fails when
                   |                            |duplicate addresses are in
                   |                            |the route table

--- Comment #73 from Juan Lang   2009-05-12 10:02:04 ---
Changing summary to reflect current state, and confirming.

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

Juan Lang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #20902|0                           |1
        is obsolete|                            |

--- Comment #74 from Juan Lang   2009-05-12 21:08:46 ---
Created an attachment (id=21068)
 --> (http://bugs.winehq.org/attachment.cgi?id=21068)
Patch

Does this help?

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #75 from chris ahrendt   2009-05-12 21:21:59 ---
wine: configuration in '/home/cahrendt/.wine' has been updated.
main.c:841: mib2IpRouteQuery: Assertion `tableIndex' failed.
wine: Assertion failed at address 0x60000832 (thread 0009), starting
debugger...
wine client error:9: read: Bad address
make: *** [main.ok] Error 1

Is what I get with the patch

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

Juan Lang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #21068|0                           |1
        is obsolete|                            |

--- Comment #76 from Juan Lang   2009-05-12 21:25:37 ---
Created an attachment (id=21069)
 --> (http://bugs.winehq.org/attachment.cgi?id=21069)
Patch take 2

Thanks for the quick feedback!  How about this?

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #77 from chris ahrendt   2009-05-12 21:30:33 ---
[cahrendt@stinky tests]$ make test
../../../tools/runtest -q -P wine -M inetmib1.dll -T ../../.. -p
inetmib1_test.exe.so main.c && touch main.ok
main.c:343: Test failed: SnmpExtensionQuery failed: 0, 0
make: *** [main.ok] Error 1

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #78 from Juan Lang   2009-05-12 22:58:24 ---
(In reply to comment #77)
> main.c:343: Test failed: SnmpExtensionQuery failed: 0, 0

Rats.  Perhaps you could post a +inetmib1 trace of this?

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #79 from chris ahrendt   2009-05-13 08:00:22 ---
[cahrendt@stinky tests]$ tail ~/inetmibpatch3.txt
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.192.150.51.0
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.192.150.51.0,
0x32fa98)
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.192.150.51.0,
0x32fa98)
trace:inetmib1:mib2IpNetQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.192.150.51.0,
0x32fa98)
trace:inetmib1:mib2IcmpQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.192.150.51.0,
0x32fa98)
main.c:343: Test failed: SnmpExtensionQuery failed: 0, 0
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:DllMain (0x0x7ba60000, 0, (nil))
make: *** [main.ok] Error 1

If you need the whole trace let me know its 4 gigs...

Will be travelling today so will check periodically if you need something as I
wait for my next flight.

Chris

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

Juan Lang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #21069|0                           |1
        is obsolete|                            |

--- Comment #80 from Juan Lang   2009-05-13 14:39:29 ---
Created an attachment (id=21075)
 --> (http://bugs.winehq.org/attachment.cgi?id=21075)
Patch take 3

How about this one?

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #81 from chris ahrendt   2009-05-13 17:05:47 ---
[cahrendt@stinky tests]$ make test
../../../tools/runtest -q -P wine -M inetmib1.dll -T ../../.. -p
inetmib1_test.exe.so main.c && touch main.ok
main.c:371: Test failed: expected type ASN_IPADDRESS, got 00
main.c:409: Test failed: SnmpExtensionQuery failed: 0, 0
make: *** [main.ok] Error 2

Then with inetmib1 winedebug

[cahrendt@stinky tests]$ make test &>~/inetmib2.txt
[cahrendt@stinky tests]$ tail ~/inetmib2.txt
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.67.183.133,
0x32fa98)
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.67.183.133,
0x32fa98)
trace:inetmib1:mib2IpNetQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.67.183.133,
0x32fa98)
trace:inetmib1:mib2IcmpQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.67.183.133,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.7.5.1.1
trace:inetmib1:mib2UdpEntryQuery (0xa1, 1.3.6.1.2.1.7.5.1.1, 0x32fa98)
main.c:409: Test failed: SnmpExtensionQuery failed: 0, 0
trace:inetmib1:DllMain (0x0x60360000, 0, (nil))
make: *** [main.ok] Error 2

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #82 from Juan Lang   2009-05-13 17:09:36 ---
(In reply to comment #81)
> [cahrendt@stinky tests]$ make test
> ../../../tools/runtest -q -P wine -M inetmib1.dll -T ../../.. -p
> inetmib1_test.exe.so main.c && touch main.ok
> main.c:371: Test failed: expected type ASN_IPADDRESS, got 00
> main.c:409: Test failed: SnmpExtensionQuery failed: 0, 0

Can you include enough of the log that the first failure, and a few lines
before it, are included too?

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #83 from chris ahrendt   2009-05-13 22:48:20 ---
the first one is all the output... I can give you more of the +inetmib1 wine
debug

[cahrendt@stinky ~]$ tail -n 40 ~/inetmib2.txt
trace:inetmib1:mib2IpAddrQuery (0xa1, 1.3.6.1.2.1.4.20.1.1.127.0.0.1, 0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.20.1.1.192.168.184.1
trace:inetmib1:mib2IpAddrQuery (0xa1, 1.3.6.1.2.1.4.20.1.1.192.168.184.1,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.20.1.1.172.16.185.1
trace:inetmib1:mib2IpAddrQuery (0xa1, 1.3.6.1.2.1.4.20.1.1.172.16.185.1,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.20.1.1.166.203.196.110
trace:inetmib1:mib2IpAddrQuery (0xa1, 1.3.6.1.2.1.4.20.1.1.166.203.196.110,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.20.1.1.9.49.221.226
trace:inetmib1:mib2IpAddrQuery (0xa1, 1.3.6.1.2.1.4.20.1.1.9.49.221.226,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.20.1.1.127.0.0.1
trace:inetmib1:mib2IpAddrQuery (0xa1, 1.3.6.1.2.1.4.20.1.1.127.0.0.1, 0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.20.1.1.192.168.184.1
trace:inetmib1:mib2IpAddrQuery (0xa1, 1.3.6.1.2.1.4.20.1.1.192.168.184.1,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.20.1.1.172.16.185.1
trace:inetmib1:mib2IpAddrQuery (0xa1, 1.3.6.1.2.1.4.20.1.1.172.16.185.1,
0x32fa98)
trace:inetmib1:mib2IpAddrQuery (0xa1, 1.3.6.1.2.1.4.20.1.1.172.16.185.1,
0x32fa98)
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.20.1.1.172.16.185.1,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1, 0x32fa98)
main.c:371: Test failed: expected type ASN_IPADDRESS, got 00
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.9.67.183.133
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.67.183.133,
0x32fa98)
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.67.183.133,
0x32fa98)
trace:inetmib1:mib2IpNetQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.67.183.133,
0x32fa98)
trace:inetmib1:mib2IcmpQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.67.183.133,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.7.5.1.1
trace:inetmib1:mib2UdpEntryQuery (0xa1, 1.3.6.1.2.1.7.5.1.1, 0x32fa98)
main.c:409: Test failed: SnmpExtensionQuery failed: 0, 0
trace:inetmib1:DllMain (0x0x60360000, 0, (nil))
make: *** [main.ok] Error 2
[cahrendt@stinky ~]$

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #84 from Juan Lang   2009-05-14 11:07:38 ---
Created an attachment (id=21096)
 --> (http://bugs.winehq.org/attachment.cgi?id=21096)
Additional patch

Could you also apply this one and let me know what happens?

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

Juan Lang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #20914|0                           |1
        is obsolete|                            |

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

Juan Lang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #20915|0                           |1
        is obsolete|                            |

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

Juan Lang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #20916|0                           |1
        is obsolete|                            |

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #85 from chris ahrendt   2009-05-14 12:43:02 ---
On top of patch 3? or by itself

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #86 from Juan Lang   2009-05-14 14:15:03 ---
(In reply to comment #85)
> On top of patch 3? or by itself

With patch 3, thanks.

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #87 from chris ahrendt   2009-05-14 15:16:49 ---
[cahrendt@stinky tests]$ make test
../../../tools/runtest -q -P wine -M inetmib1.dll -T ../../.. -p
inetmib1_test.exe.so main.c && touch main.ok
main.c:409: Test failed: SnmpExtensionQuery failed: 0, 0
make: *** [main.ok] Error 1

+inetmib1 output...

[cahrendt@stinky tests]$ tail -n 40 ~/inetmib3.txt
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.204.146.46.90
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.204.146.46.90,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.204.146.166.107
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.204.146.166.107,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.129.37.0.113
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.129.37.0.113,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.32.97.166.118
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.32.97.166.118,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.32.97.115.132
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.32.97.115.132,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.32.97.115.146
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.32.97.115.146,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.32.97.115.218
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.32.97.115.218,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.32.97.118.242
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.32.97.118.242,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.32.97.118.243
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.32.97.118.243,
0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.0.0.0.0
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.0.0.0.0, 0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.4.21.1.1.9.0.0.0
trace:inetmib1:mib2IpRouteQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.0.0.0, 0x32fa98)
trace:inetmib1:mib2IpNetQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.0.0.0, 0x32fa98)
trace:inetmib1:mib2IcmpQuery (0xa1, 1.3.6.1.2.1.4.21.1.1.9.0.0.0, 0x32fa98)
trace:inetmib1:SnmpExtensionQuery (0xa1, 0x32fd8c, 0x32fd98, 0x32fd94)
trace:inetmib1:SnmpExtensionQuery 1.3.6.1.2.1.7.5.1.1
trace:inetmib1:mib2UdpEntryQuery (0xa1, 1.3.6.1.2.1.7.5.1.1, 0x32fa98)
main.c:409: Test failed: SnmpExtensionQuery failed: 0, 0
trace:inetmib1:DllMain (0x0x60330000, 0, (nil))
make: *** [main.ok] Error 1

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #88 from Juan Lang   2009-05-14 17:54:26 ---
(In reply to comment #87)
> [cahrendt@stinky tests]$ make test
> ../../../tools/runtest -q -P wine -M inetmib1.dll -T ../../.. -p
> inetmib1_test.exe.so main.c && touch main.ok
> main.c:409: Test failed: SnmpExtensionQuery failed: 0, 0
> make: *** [main.ok] Error 1

I think this is an improvement.  The first patch should eliminate the endless
loop you were seeing, though it does introduce two test failures.  The second
patch eliminates one of the test failures.  I'm not sure what the cause of the
second is yet.  I think I'll send in the two patches I have, wait for those to
settle down a bit, then I'll come back at the second failure in a few days.

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #89 from chris ahrendt   2009-05-14 20:08:26 ---
works for me... let me know if you need anything further before our second
round of debugging lol...

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #90 from Juan Lang   2009-05-15 12:11:22 ---
(In reply to comment #89)
> works for me... let me know if you need anything further before our second
> round of debugging lol...

Out of curiosity, is this on an up-to-date tree?  Would you mind getting
today's git and trying again?  No need to apply any supplemental patches to it.

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #91 from chris ahrendt   2009-05-15 19:48:34 ---
just did a GIT of the latest tree and here is the make test result:

[cahrendt@stinky tests]$ make test
../../../tools/runtest -q -P wine -M inetmib1.dll -T ../../.. -p
inetmib1_test.exe.so main.c && touch main.ok
main.c:409: Test failed: SnmpExtensionQuery failed: 0, 0
make: *** [main.ok] Error 1

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

--- Comment #92 from Austin English   2009-11-19 12:53:15 ---
This is your friendly reminder that there has been no bug activity for 6
months. Is this still an issue in current (1.1.33 or newer) wine?

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

chris ahrendt  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #93 from chris ahrendt   2009-11-19 21:02:45 ---
Fixed ... no exception anymore... closing

[Bug 17996] inetmib1 test fails when duplicate addresses are in the route table

http://bugs.winehq.org/show_bug.cgi?id=17996

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #94 from Alexandre Julliard   2009-12-04 12:15:59 ---
Closing bugs fixed in 1.1.34.