Subject: bug#34373: closed (Re: bug#34373: Acknowledgement (26.1; Missing range check in rx-submatch-n))

From: [email-masked] (GNU bug Tracking System)
Date: Sun, 23 Jun 2019 18:35:03 +0000

Your bug report

#34373: 26.1; Missing range check in rx-submatch-n

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
34373: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34373
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#34373: Acknowledgement (26.1; Missing range check in rx-submatch-n)
From: Mattias Engdegård <[email-masked]>
To: Lars Ingebrigtsen <[email-masked]>
Cc: [email-masked]
Date: Sun, 23 Jun 2019 20:34:07 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

23 juni 2019 kl. 20.20 skrev Lars Ingebrigtsen <[email-masked]>:
> 
> This looks like an eminently reasonable sanity check to me, but I'm
> quite unfamiliar with the rx machinery.  Just push the change?

Thank you, pushed.

Subject: 26.1; Missing range check in rx-submatch-n
From: Mattias Engdegård <[email-masked]>
To: [email-masked]
Date: Thu, 7 Feb 2019 19:01:33 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

`rx' should protect its own abstractions and never generate an invalid regexp, but will if given a bad submatch number:

(rx (group-n 0 "x"))
=> "\\(?0:x\\)"

It's a missing range check in rx-submatch-n.

In GNU Emacs 26.1 (build 1, x86_64-apple-darwin14.5.0, NS appkit-1348.17 Version 10.10.5 (Build 14F2511))
 of 2018-05-31 built on builder10-10.porkrind.org
Windowing system distributor 'Apple', version 10.3.1671