On Feb 9, 2011, at 10:59 AM, Martin Mathieson wrote:
> Hi Manjula,
>
> I can't view those attached images.
You're assuming there *are* attached images. What's in the HTML part of the message is stuff such as
<div><font color=3D"#0000FF"><img src=3D"rtfimage://" width=3D"1280" height=
=3D"957"></font></div>
which appears to lack an actual, err, umm, *image*.
Earlier in the message it says
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
Remind me never ever ever ever ever ever ever to ask a Microsoft Exchange Server to convert RTF to HTML if the RTF document contains images, as it appears to do a really bad job of it.
However, as you note:
> More useful than the captures though would be the captured files that lead to the crash.
"wireshark has encountered error and need to close", in the Windows GUI, is equivalent to "{Segmentation fault, Bus error, Abort, ...} - core dumped" at the UN*X command line or various other messages which give, in general, far too little information to allow any diagnosis whatsoever. Unless the error dialog gives something such as a stack trace, it probably won't help us figure out why Wireshark is crashing. If we open the captured file, however, and Wireshark crashes, we may be able to point a debugger at it and see exactly where it's crashing, which could help indicate *why* it's crashing.
