http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=54872
User: guy
Date: 2014/01/21 08:50 AM
Log:
Check the return of wtap_dump_close() even if we've gotten a read error;
the only reason not to check it is if we've already gotten a write error
and another write error would be superfluous (either "you got two of the
same error" or "you got an I/O error *and* you ran out of disk
space/disk quota" is of limited interest).
Discard the return value of wtap_dump_close() in the case where we've
already gotten a write error, in the hopes of squelching a Coverity
warning.
Directory: /trunk/
Changes Path Action
+10 -3 file.c Modified
+10 -3 mergecap.c Modified