public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "makovick at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/14780] [PATCH] handle malloc() and realloc() failures in regcomp() Date: Sun, 28 Oct 2012 13:29:00 -0000 [thread overview] Message-ID: <bug-14780-132-66wUMO5NH6@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14780-132@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14780 --- Comment #3 from Jindrich Makovicka <makovick at gmail dot com> 2012-10-28 13:28:54 UTC --- I have been debugging this issue by fuzzing re_malloc() and re_realloc(), making them randomly return NULL. The patch with added fuzzing is attached as regex-fuzzed.diff . testcase.c has been used to exercise the modified regcomp(). Memory violations or leaks have been tested using valgrind: valgrind --leak-check=full --show-reachable=yes --trace-children=yes ./testrun.sh ./testcase -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-10-28 13:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-28 13:27 [Bug regex/14780] New: " makovick at gmail dot com 2012-10-28 13:28 ` [Bug regex/14780] " makovick at gmail dot com 2012-10-28 13:28 ` makovick at gmail dot com 2012-10-28 13:29 ` makovick at gmail dot com [this message] 2012-10-28 14:42 ` makovick at gmail dot com 2013-01-17 14:10 ` siddhesh at redhat dot com 2013-09-12 3:26 ` bugdal at aerifal dot cx 2013-09-12 17:21 ` makovick at gmail dot com 2013-09-14 16:50 ` bugdal at aerifal dot cx 2013-10-14 16:10 ` neleai at seznam dot cz
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-14780-132-66wUMO5NH6@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs-regex@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).