http://bugs.winehq.org/show_bug.cgi?id=10401
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #1 from Dan Kegel dank@kegel.com 2008-03-18 21:34:35 --- (Did you get the names of those binaries backwards?)
In the successful case, cygwin1.dll's scanf is called. In the failure case, WINEDEBUG=+all shows no calls between program entry and failure, so I suspect you've linked in a static library that implements sscanf. You'd need to step through that library with a debugger to figure out what's going on.