[prev in list] [next in list] [prev in thread] [next in thread]
List: llvm-dev
Subject: Re: [LLVMdev] Asan: Print stacktrace on SIGFPE
From: David Jones <djones () xtreme-eda ! com>
Date: 2015-07-31 16:45:44
Message-ID: CAEwg-QLo0rKuAQAt_G0TWfjHmxddwzHzR-zniB1UYZGriNAf-w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
SIGFPE is thrown (at least on Linux x86_64) for integer divide by zero.
This sounds like a worthy target for a fuzzer.
On Fri, Jul 31, 2015 at 12:32 PM, Kostya Serebryany <kcc@google.com> wrote:
>
>
> On Fri, Jul 31, 2015 at 5:15 AM, Karl Skomski <karl@skomski.com> wrote:
>
>> Would it make sense to add the possibility to print a stacktrace also on
>> SIGFPE and not only on SIGSEGV or SIGBUS?
>>
>
> Yes, under a separate flag (handle_sigfpe=1).
> I think it's fine to have this flag on by default.
> Would you like to contribute a patch?
>
>
>> Only noticed that LibFuzzer doesn't generate any crash report because
>> asan is not handling the signal.
>>
>
> Makes sense. The sanitizers (except maybe a bit of ubsan) typically don't
> deal with floating point errors,
> so no one cared about SIGFPE. But libFuzzer may discover some of those
> errors.
>
> --kcc
>
>
>>
>> Kind regards,
>>
>> Karl Skomski
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev@cs.uiuc.edu http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
>>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev@cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
[Attachment #5 (text/html)]
<div dir="ltr"><div>SIGFPE is thrown (at least on Linux x86_64) for integer divide by \
zero.<br><br></div>This sounds like a worthy target for a fuzzer.<br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 31, 2015 at 12:32 PM, \
Kostya Serebryany <span dir="ltr"><<a href="mailto:kcc@google.com" \
target="_blank">kcc@google.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div \
class="gmail_quote">On Fri, Jul 31, 2015 at 5:15 AM, Karl Skomski <span \
dir="ltr"><<a href="mailto:karl@skomski.com" \
target="_blank">karl@skomski.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><span \
style="font-size:12.8000001907349px">Would it make sense to add the possibility to \
print a stacktrace also on SIGFPE and not only on SIGSEGV or \
SIGBUS?</span></div></blockquote><div><br></div><div>Yes, under a separate flag \
(handle_sigfpe=1). </div><div>I think it's fine to have this flag on by default. \
</div><div>Would you like to contribute a patch? </div><div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div style="font-size:12.8000001907349px">Only \
noticed that LibFuzzer doesn't generate any crash report because asan is not \
handling the signal.<br></div></div></blockquote><div><br></div><div>Makes sense. The \
sanitizers (except maybe a bit of ubsan) typically don't deal with floating point \
errors, </div><div>so no one cared about SIGFPE. But libFuzzer may discover some of \
those errors. </div><div><br></div><div>--kcc </div><div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div \
style="font-size:12.8000001907349px"><div><br>Kind regards,<br><br>Karl \
Skomski</div></div> </div>
<br>_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> \
<a href="http://llvm.cs.uiuc.edu" rel="noreferrer" \
target="_blank">http://llvm.cs.uiuc.edu</a><br> <a \
href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" rel="noreferrer" \
target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br> \
<br></blockquote></div><br></div></div> \
<br>_______________________________________________<br> LLVM Developers mailing \
list<br> <a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a \
href="http://llvm.cs.uiuc.edu" rel="noreferrer" \
target="_blank">http://llvm.cs.uiuc.edu</a><br> <a \
href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" rel="noreferrer" \
target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br> \
<br></blockquote></div><br></div>
_______________________________________________
LLVM Developers mailing list
LLVMdev@cs.uiuc.edu http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic