public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/15078] regex crash on myanmar script
Date: Wed, 30 Jan 2013 10:18:00 -0000 [thread overview]
Message-ID: <bug-15078-132-hbxvwrv8pQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15078-132@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15078
--- Comment #1 from Paolo Bonzini <bonzini at gnu dot org> 2013-01-30 10:17:41 UTC ---
valgrind complains:
==10965== Invalid write of size 8
==10965== at 0x35F8689563: __GI_memset (in /usr/lib64/libc-2.16.so)
==10965== by 0x35F86CA636: clean_state_log_if_needed (in
/usr/lib64/libc-2.16.so)
==10965== by 0x35F86D60C6: re_search_internal (in /usr/lib64/libc-2.16.so)
==10965== by 0x35F86D67E4: re_search_stub (in /usr/lib64/libc-2.16.so)
==10965== by 0x35F86D7087: re_search (in /usr/lib64/libc-2.16.so)
==10965== by 0x407B3A: match_regex (regexp.c:252)
==10965== by 0x406AFB: execute_program (execute.c:1189)
==10965== by 0x4077BF: process_files (execute.c:1857)
==10965== by 0x402496: main (sed.c:366)
==10965== Address 0x4c47fb8 is 0 bytes after a block of size 104 alloc'd
==10965== at 0x4A08A2E: realloc (vg_replace_malloc.c:662)
==10965== by 0x35F86CA4B2: extend_buffers (in /usr/lib64/libc-2.16.so)
==10965== by 0x35F86CA5D2: clean_state_log_if_needed (in
/usr/lib64/libc-2.16.so)
==10965== by 0x35F86D60C6: re_search_internal (in /usr/lib64/libc-2.16.so)
==10965== by 0x35F86D67E4: re_search_stub (in /usr/lib64/libc-2.16.so)
==10965== by 0x35F86D7087: re_search (in /usr/lib64/libc-2.16.so)
==10965== by 0x407B3A: match_regex (regexp.c:252)
==10965== by 0x406AFB: execute_program (execute.c:1189)
==10965== by 0x4077BF: process_files (execute.c:1857)
==10965== by 0x402496: main (sed.c:366)
==10965==
--
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:[~2013-01-30 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 11:44 [Bug regex/15078] New: " bonzini at gnu dot org
2013-01-30 10:18 ` bonzini at gnu dot org [this message]
2013-01-30 16:20 ` [Bug regex/15078] " carlos at systemhalted dot org
2013-01-30 18:29 ` carlos at systemhalted dot org
2013-02-12 8:32 ` schwab@linux-m68k.org
2014-02-16 19:35 ` jackie.rosen at hushmail dot com
2014-05-28 19:46 ` schwab at sourceware dot org
2014-05-28 19:46 ` schwab at sourceware dot org
2014-06-13 18:58 ` [Bug regex/15078] regex crash on myanmar script (CVE-2013-0242) fweimer at redhat dot com
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-15078-132-hbxvwrv8pQ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs-regex@sourceware.org \
/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: link
Be 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).