This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/2] Demangler crash handler
- From: Gary Benson <gbenson at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Mark Kettenis <mark dot kettenis at xs4all dot nl>, gdb-patches at sourceware dot org
- Date: Thu, 15 May 2014 15:28:04 +0100
- Subject: Re: [PATCH 0/2] Demangler crash handler
- Authentication-results: sourceware.org; auth=none
- References: <20140509100656 dot GA4760 at blade dot nx> <201405091120 dot s49BKO1f010622 at glazunov dot sibelius dot xs4all dot nl> <20140509153305 dot GA13345 at blade dot nx> <201405112023 dot s4BKNL3v024248 at glazunov dot sibelius dot xs4all dot nl> <20140513102134 dot GB17805 at blade dot nx> <537242D9 dot 7080101 at redhat dot com> <20140515132408 dot GC13323 at blade dot nx> <5374CA2B dot 90509 at redhat dot com>
Pedro Alves wrote:
> On 05/15/2014 02:24 PM, Gary Benson wrote:
> > > Though a fuzzy tester that throws pseudo-random symbols at it
> > > would be a nice project on its own.)
> >
> > I have a fuzzer for it. <http://gbenson.net/?p=422>.
>
> Nice!
>
> I took a peek. I suggest wrapping it in a SIGSEGV handler so
> the it prints the symbol that crashes. :-) That way one can
> leave it running for a few hours, without needing to have core
> dumps enabled.
I could do that :)
The way I imagined using it right now would be to run to a fault,
then fix that fault. The rate it finds crashes you'd get 1000 an
hour easily, but they might all be the same three bugs.
I'm working on some other stuff now, but I might make it my task
to fix demangler bugs here and there between projects. I pretty
much have a handle on it now I think.
Cheers,
Gary