public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot bonzini at lu dot unisi dot ch" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/934] segfault in regexec
Date: Fri, 06 May 2005 07:37:00 -0000	[thread overview]
Message-ID: <20050506073712.9933.qmail@sourceware.org> (raw)
In-Reply-To: <20050506060600.934.zachmann@schlund.de>


------- 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.


  reply	other threads:[~2005-05-06  7:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06  6:06 [Bug regex/934] New: " zachmann at schlund dot de
2005-05-06  7:37 ` paolo dot bonzini at lu dot unisi dot ch [this message]
2005-05-06  8:13 ` [Bug regex/934] " zachmann at schlund dot de
2005-05-06  8:19 ` paolo dot bonzini at lu dot unisi dot ch
2005-05-06  8:26 ` jakub at redhat dot com
2005-07-18  2:51 ` cvs-commit at gcc dot gnu dot org
2005-07-18  2:52 ` roland at gnu dot org
2005-07-19  3:31 ` roland at gnu dot org

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=20050506073712.9933.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --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: 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).