[Bug 815] - msvcrt20 and msvcrt incompatibility

http://bugs.winehq.com/show_bug.cgi?id=815

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

------- Additional Comments From [e-mail]  2002-06-21 16:22 -------
ooook, now I see what the problem is...
(well, not quite, but much further)

Our builtin msvcrt20 has a __getmainargs *forward* entry, which thus calls
into native msvcrt __getmainargs.
For some reason the program seems to call our msvcrt20 __getmainargs with
new_mode set to NULL, which crashes native msvcrt, as it assumes that new_mode
is *never* NULL.
Can you try to find out why the program calls __getmainargs with new_mode set to
NULL ?
We need to know whether msvcrt20 __getmainargs can indeed be legally called with
a NULL new_mode.
If so, then we'd have to get rid of the forward to msvcrt __getmainargs, as
native msvcrt obviously has a problem with a NULL parameter here.
(IOW: we'd have to actually implement a msvcrt20 __getmainargs function that
calls into msvcrt __getmainargs, with a NULL new_mode check added)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://bugs.winehq.com/show_bug.cgi?id=815.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.