public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Dieperink Alwin <alwin.dieperink@elca.ch>
To: "'help-gnats@gnu.org'" <help-gnats@gnu.org>
Subject: Categories containing "++" make gnatsweb crash
Date: Mon, 20 Jan 2003 14:34:00 -0000	[thread overview]
Message-ID: <A13B47F8EC3FD111A91500C04FD2A282021FA604@exchange.elca.ch> (raw)

Hello,

When categories contain a "++" in their name, gnatsweb crashes with the
following error:

	Nested quantifiers in regex; marked by <-- HERE in m/^client-c++ <--
HERE $/ at /home/gnats/cgi-bin/gnatsweb.pl line 1610, <SOCK> line 2173.

which points to the line containing grep in this piece of code:

	sub edit
	...
	    if (fieldinfo ($_, 'fieldtype') eq 'enum')
	    {
	      my $default = $fields{$_};
	      # Check whether field value is a known enumeration value.
	      if (!(grep /^$default$/, @$values))
	      {
	        push(@$values, 'unknown') if (!grep /^unknown$/, @$values);
	        $default = 'unknown';
	      }
	      print popup_or_scrolling_menu($_, $values, $default),
	            "</td>\n</tr>\n";
	    }
	...

When I replaced the name of the category client-c++ with client-cpp and made
all necessary changes in the PR's it works fine. The example file
"categories" doesn't warn against this and in there is an example which
wouldn't work (g++).

There are several solutions:
1) restrict the use of special characters in category names and correct
"categories"
2) correct the use of grep in gnatsweb.
3) ...

My preference goes actually to the first solution.

Regards
-- Alwin

Environment: Gnatsweb v3.99.4, Gnats v4.0-beta2





_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

             reply	other threads:[~2003-01-20 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 14:34 Dieperink Alwin [this message]
2003-04-29 19:47 ` Yngve Svendsen
2003-05-05 17:48   ` Lars Henriksen
2003-05-06  9:31     ` Yngve Svendsen
2003-05-06 21:13     ` Yngve Svendsen

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=A13B47F8EC3FD111A91500C04FD2A282021FA604@exchange.elca.ch \
    --to=alwin.dieperink@elca.ch \
    --cc=help-gnats@gnu.org \
    /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).