https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14281
Guy Harris <g...@alum.mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DUPLICATE |---
Status|RESOLVED |UNCONFIRMED
--- Comment #4 from Guy Harris <g...@alum.mit.edu> ---
This may be a problem with a network share, but it's not clear that it's the
*same* problem - in this bug, an fwrite() call got ENOENT, which the Visual
Studio C library appears to be returned for:
ERROR_FILE_NOT_FOUND
ERROR_PATH_NOT_FOUND
ERROR_INVALID_DRIVE
ERROR_NO_MORE_FILES
ERROR_BAD_NETPATH
ERROR_BAD_NET_NAME
ERROR_BAD_PATHNAME
ERROR_FILENAME_EXCED_RANGE
some of which *might* show up on a write if the file was successfully opened
but is no longer available (because the server is down or the connection was
broken), but in the other bug, an fwrite() call got EINVAL, which is returned
for pretty much anything that the VS C library doesn't have anything else to
map it to.
In addition, *this* bug also got a crash, which the other bug didn't.
So there are at least two issues:
1) we shouldn't be using errno values on Windows, we should be using _doserror
values, so that we don't lose information due to the VS C library mapping
Windows error codes to "generic" errors such as EINVAL or to inappropriate
values such as ENOENT (ERROR_FILENAME_EXCED_RANGE sounds as if it should be
treated as ENAMETOOLONG, not ENOENT);
2) TShark crashed.
This bug should track issue 2), even if we let the other bug track issue 1).
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
