https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4115
--- Comment #20 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2010-04-27 11:00:48 PDT ---
(In reply to comment #18)
> > Is this a 32- or 64-bit process? (Running 'file' on the wireshark executable
> > should tell you.)
>
> I guess it is the 32 bit edition - I just picked it from the download menu at
> wireshark.org.
Ah, I suppose that makes sense if we continue to support older versions
(pre-Leopard?) of MacOS.
> I'm fully aware I cannot load terabytes of traces ;-)
> But on the windows edition it get a error message telling me the trace cannot
> be loaded - before the program aborts.
That's just luck. When Wireshark's own memory allocation routines fail, we can
display the dialog and call it quits "gracefully." But when the allocations
fail in GLIB or GTK (two libraries that Wireshark uses), we're out of luck: the
libraries simply call abort() and we die (without a friendly dialog).
Anyway, sounds like there's no issue left unexplained here, right?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
