This is the mail archive of the
glibc-bugs-regex@sources.redhat.com
mailing list for the glibc project.
[Bug regex/934] segfault in regexec
- From: "jakub at redhat dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs-regex at sources dot redhat dot com
- Date: 6 May 2005 08:26:14 -0000
- Subject: [Bug regex/934] segfault in regexec
- References: <20050506060600.934.zachmann@schlund.de>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From jakub at redhat dot com 2005-05-06 08:26 -------
Or the whole re_search_internal. Depends on how common is using the same
regex_t simultaneously. I think it is uncommon, and therefore just
locking/unlocking it once should be faster than finding out which places
ever touch anything reachable from regex_t and adding locks to all those
places.
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=934
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.