I'm working on MR 23103 (not really relevant/required for my questions) and it's failing some of the automated Python test suite, specifically:test_wireshark_capture_10_packets_to_file test_wireshark_capture_from_stdin test_wireshark_capture_snapshot_len
I've bisected the patch down to the smallest change possible of the pass/fail criteria, but I'm still not having any luck identifying the (code) problem. The failures are "heap corruption", which I can see as a possibility given my code changes, but a call stack when it happens would go a long way to helping me hunt down the source of problem.Many times previously I could look at what the suite test is doing and run the individual capture file in Wireshark/tshark to find the source of my problem. But it looks like these tests are piping "static" capture files through to Wireshark (so they look like captured packets). Am I reading that correctly? (my Python skills are beginner level). Any tips to potentially hook this up to a debugger (MSVC on Windows) or generating a crash report? Or steps to reproduce the test in MSVC (without Python)?
_______________________________________________ Wireshark-dev mailing list -- [email protected] To unsubscribe send an email to [email protected]
