Bug 199000
Summary: | Seg fault pointing to glibc-2.4-8. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom Browder <tbrowder> | ||||
Component: | glibc | Assignee: | Jakub Jelinek <jakub> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-07-17 06:29:32 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Tom Browder
2006-07-15 15:26:27 UTC
Created attachment 132490 [details]
Test program to demonstrate the Electric Fence diagnostic pointing to glibc.
*** Bug 199003 has been marked as a duplicate of this bug. *** 1. I forgot to add the header for the test case, but all it does is declare the "regex_match" function: bool regex_match(const std::string& regex, const std::string& s, const bool case_sensitive = true); 2. Note that I tested the "regex_match" function using const char pointers instead of std strings and got the same results. And the same failure occurs without the empty regex and test strings. Note some other errors seem to be evident. When I used the Boost regex library instead of glibc on the identical set of test strings and regexes, Boost threw an exception on the regex "\\([csu])\\)" which has an unmatched right parenthesis. That may not be a POSIX error, but it should be. In addition, no errors were indicated by the regexec function for an empty regex (""). You just need to use EF_ALLOW_MALLOC_0=1 in the environment for this testcase, allocating 0 bytes here is not a bug. |