[Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx>]

In my case it turned out to be a private dissector with a change that I had forgotten that I hadn't tested.  Annoyingly, I had to step/binary-chop in the debugger with breakpoints until I could step in to the crash itself (which was in the proto_register_...() for that dissector.  There was an odd crash (something to do with interfaces) after fixing this, which went away after I restored the preferences, etc files.  I have since tried hiding the files again but can't seem to get back to that crash.

Martin

On Thu, Dec 19, 2013 at 4:42 PM, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:

On 19 December 2013 16:00, Christopher Maynard <Christopher.Maynard@xxxxxxxxx> wrote:

Martin Mathieson <martin.r.mathieson@...> writes:

> My windows build (from current trunk) is crashing upon startup today, with
the error "This application has requested the Runtime to terminate in an
unusual way".  The usual steps to get rid of this, i.e. doing a 'clean', or
a 'setup' and 'clean' don't make any difference.  And running within MSVC
2010 EE with all of the Exceptions turned on doesn't give any more information.
>
> Is it just me?

I just updated to r54248, did a distclean and then recompiled using MSVC
2010 EE.  I'm running fine on Windows 7 x64.  I'm currently configured for gtk2.

I would check your preferences.  In the past I encountered a similar startup
problem to what you're experiencing, and in my case it was due to a problem
with the snmp_users file.  You may want to just temporarily move all files
out of your personal configuration folder and see if it makes any difference
to startup.  If it does, then "divide and conquer" to find the offending
file(s).

Good luck!
- Chris

With r54249, I see a similar issue to Martin.  A quick look with WinDbg shows it to be in airpcap_loader.c, function test_if_on() where the boolp member of the preference is dereferenced.  In my case it's 0xbaadf00d, i.e. uninitialized.  I don't have time at the moment to look any further, but I suspect this would impact all users who upgrade to this 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