Tue Aug 7 11:29:35 PDT 2012
- Previous message: [Slony1-bugs] [Bug 272] slonik can segfault scanning input
- Next message: [Slony1-bugs] [Bug 275] New: monitor_thread leaks memory
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=272 --- Comment #9 from Steve Singer <ssinger at ca.afilias.info> 2012-08-07 11:29:35 PDT --- I think YYABORT is a yacc macro not a flex one: scan.l: In function ‘yylex’: scan.l:170: error: ‘YYABORT’ undeclared (first use in this function) scan.l:170: error: (Each undeclared identifier is reported only once scan.l:170: error: for each function it appears in.) yyterminate() compiles, but I am not sure if that will do what we want. I don't think that tells yacc/bison that this is an abnormal termination versus a normal one. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 272] slonik can segfault scanning input
- Next message: [Slony1-bugs] [Bug 275] New: monitor_thread leaks memory
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list