public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: FaUl <immo.gccbug@faul.dyndns.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/6509: endless-loop in C-parser while parsing struct with forgotten ',' Date: Tue, 30 Apr 2002 02:56:00 -0000 [thread overview] Message-ID: <20020430095603.11414.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6509; it has been noted by GNATS. From: FaUl <immo.gccbug@faul.dyndns.org> To: jakub@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, immo.gccbug@faul.dyndns.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c/6509: endless-loop in C-parser while parsing struct with forgotten ',' Date: Tue, 30 Apr 2002 11:46:14 +0200 --p4qYPpj5QlsIQJ0K Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hallo jakub, du schrobst: > Synopsis: endless-loop in C-parser while parsing struct with forgotten ',' > > State-Changed-From-To: open->feedback > State-Changed-By: jakub > State-Changed-When: Tue Apr 30 02:17:20 2002 > State-Changed-Why: > You forgot to include the testcase. Sorry, it was the first time I try the gccbug-script... I've attached it now... FaUl -- Brain 1.0, sollte eigentlich bei jedem Humanoiden dabeisein - jedoch zeigt die Praxis, das oft bei der auslieferung geschlampt wird und viele mit einer pre-release von Brain ausgeliefert werden. (oder ganz ohne) [Juergen P. Meier in dcsf] --p4qYPpj5QlsIQJ0K Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="bug.c" typedef unsigned short int port_t; #define NVAL 0 #define IVAL 1 #define PVAL 2 #define SVAL 3 #define CVAL 4 #define FVAL 5 const struct { char *key; char arg; union { unsigned int* ival; port_t* pval; char** sval; unsigned char* cval; void (*fval) (void); } val; char what; const char *help; int ch_bitmask; int cf_bitmask; } config_keys[] = { {"user-database", 'u', {&config.passwd}, SVAL, "file\tuse file as user-database", CHANGED_PASSWD, 0}, {"logfile",'l' ,{&config.logfile},SVAL, "file\tuse file as log-datei (or SYSLOG to use syslog)", CHANGED_LOGFILE,0}, {"dbsocket-path", 's', {&config.dbserver}, SVAL, "path to dbserver-executable", CHANGED_DBSERVER, 0}, {"loglevel", 'L', {&config.loglevel}, CVAL, "num\tloglevel (0-255)", CHANGED_LOGLEVEL, 0}, {"interface", 'i', {&config.interface}, SVAL, "interface\tinterface to bind", CHANGED_IF, 0}, {"port",'p', {&config.port}, PVAL, "port\tportnumber where ipserv listenes on", CHANGED_PORT, 0}, {"debug", 'd', {&config.debug}, CVAL, "level\tdebug level (0-255)", CHANGED_DEBUG, 0}, {"backround", 'D', {NULL}, NVAL, "\twether to fork to backround (not if set)", CHANGED_FTB, CONFIG_FTB}, {"timeout", 't'dasfasfd, {&config.timeout}, IVAL, "time\ttime until server closes the connection", CHANGED_TIMEOUT, 0}, {"version", 'v', {version}, FVAL, "\tprint version-info", 0, 0 } {"config", 'c', {&config.config}, SVAL, "file\tuse file as configuration-file", 0, 0}, {"help", 'h', {help}, FVAL, "\tprint this text", 0, 0}, {NULL} }; /* keys for configuration-parser */ --p4qYPpj5QlsIQJ0K--
next reply other threads:[~2002-04-30 9:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-30 2:56 FaUl [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-13 2:18 neil 2002-07-12 20:16 Andrew Pinski 2002-04-30 3:01 jakub 2002-04-30 2:17 jakub 2002-04-29 11:36 immo.gccbug
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=20020430095603.11414.qmail@sources.redhat.com \ --to=immo.gccbug@faul.dyndns.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.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: linkBe 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).