This is the mail archive of the glibc-bugs@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug regex/934] segfault in regexec


------- Additional Comments From paolo dot bonzini at lu dot unisi dot ch  2005-05-06 07:37 -------
Subject: Re:  New: segfault in regexec

zachmann at schlund dot de wrote:

>During the development of a multi threaded application on a multi processor 
>machine I found a segfault in regexec. I could not reproduce this crash on a 
>single processor machine.
>
Probably, trying with a long running regex would make the crash almost 
100% reproducible on both single and multi-processor machines.  I'd try 
with ^(.)?(.?)(.?)(.?)(.?)\5\4\3\2\1$ for example.

>Program terminated with signal 11, Segmentation fault. 
>#0  0x0805eb1e in re_acquire_state_context () 
>
regexec is not reentrant, because it includes a cache of DFA states in 
regex_t.

Paolo


-- 


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]