RE: stack overflow in regex engine

2024-05-22 Thread mark.yagnatinsky
Makes sense, thanks! From: Philip Race Sent: Wednesday, May 22, 2024 2:41 PM To: Yagnatinsky, Mark : IT (NYK) ; core-libs-dev@openjdk.org Subject: Re: stack overflow in regex engine CAUTION: This email originated from outside our organisation - philip.r...@oracle.com<mailto:phili

Re: stack overflow in regex engine

2024-05-22 Thread Philip Race
om:*Philip Race *Sent:* Wednesday, May 22, 2024 11:54 AM *To:* Yagnatinsky, Mark : IT (NYK) ; core-libs-dev@openjdk.org *Subject:* Re: stack overflow in regex engine CAUTION: This email originated from outside our organisation - philip.r...@oracle.com Do not click on links, open attachments, or

RE: stack overflow in regex engine

2024-05-22 Thread mark.yagnatinsky
he original author might never be heard from again. Anyway, thanks a bunch for responding; I was worried that no one would. From: Philip Race Sent: Wednesday, May 22, 2024 11:54 AM To: Yagnatinsky, Mark : IT (NYK) ; core-libs-dev@openjdk.org Subject: Re: stack overflow in regex engine CAUTION:

Re: stack overflow in regex engine

2024-05-22 Thread Philip Race
P4 is the default JBS priority, so sometimes it just means no one figured out the true priority. But in general P4 bugs could be open for years, or even never get fixed. The priority is also partially an assessment of where it falls as a priority for the JDK developers. A user of JDK may have a

stack overflow in regex engine

2024-05-21 Thread mark.yagnatinsky
(Sorry about my previous "do I need to subscribe?" email; in retrospect that was needless noise.) The purpose of this email is twofold: first, inquire about the status of ticket filed a few years ago, and second to point out some non-obvious reasons why it might be slightly more serious than it