Comment # 24
on bug 8431
from Evan Huus
(In reply to comment #23)
> Created attachment 10236 [details]
> Add ddd debugger launch capabilities to test-fuzzed
>
> I added a -d option to launch ddd for the test-fuzzed replay script. As a
> non-C guru it was not clear to me that you need to
> 1. re-run with random environment variables to get the same failure as fuzz
> and
> 2. run everything from libtool
I like the idea, not 100% sure of the implementation. I'll give it some
thought, but I agree that something like this would be good. I did mention the
'special debugging flags' already on the wiki page (in the section on
reproducing fuzz-test failures). The libtool thing is not really my area of
expertise, I just use it :P
> hopefully this can make it to the fuzz page and help the next person. A
> link from there to http://wiki.wireshark.org/Development/Tips would be great
> too.
Good idea. I will fit that in somewhere.
> Also, it would be nice if there were a way to turn off -O2 easily so the
> debugger is more effective. I manually hacked configure and did a make
> clean, but perhaps there is an easier way.
Not that I'm aware of. I've just gotten used to debugging optimized code, which
is a terrible answer, I know. If you think of something better, patches are
welcome :)
You are receiving this mail because:
- You are watching all bug changes.