iphlpapi.dll--help! (take 2)

[Juan Lang]

Prev guess about wrong ioctl being called was wrong. 
Looks like some kind of stack corruption, only when
called from wsock32.  iphlpapi works fine.

I tried to trace what's up with some printouts.  I
have a stack variable ndx, and with code like:
FIXME("ndx is %d, at %x\n", ndx, &ndx);
ndx += 4;
FIXME("ndx is %d, at %x\n", ndx, &ndx);

I see output like:
ndx is 0, at 40670b80
ndx is 101683072, at 40670b80

Umm.. anyone have any clues what's special about
wsock32?

I'll post code shortly for some kind soul to play
with.
--Juan

--- "Dimitrie O. Paun" <dimi at intelliware.ca> wrote:
> On Wed, 30 Apr 2003, Juan Lang wrote:
> 
> > Email me if interested.  No, it's not vaporware,
> it's
> > just not as well tested as I'd like.
> 
> Just send it over to wine-devel for comments, or
> wine-patches
> for inclusion into the tree.
> 
> -- 
> Dimi.
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com