On Feb 4, 2009, at 4:27 PM, Bill Meier wrote:

> My first guess would be "out of memory".

Although for that I'd expect either

       1) "Access violation reading location 0x00000000" (or some other
small value), i.e. a null-pointer dereference from something that did
a malloc() and didn't check whether it succeeded

or

       2) an assertion failure message from g_malloc() calling abort() on
failure (I think abort() failures turn up as a unique type of failure
on Windows).

Is there an "etherXXXXXX" file, for some value of "XXXXXX", in your
(Joshua's) temporary file directory?  (I forget where Windows hides
the per-user temporary file directory.)  If so, does Wireshark crash
if you try to read it?

(Also, what happens with Wireshark 1.0.5, the current version?)

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe