Tue Aug 7 10:05:02 PDT 2012
- Previous message: [Slony1-bugs] [Bug 272] slonik can segfault scanning input
- Next message: [Slony1-bugs] [Bug 258] cleanup thread can block waiting on a lock
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=272 --- Comment #7 from Steve Singer <ssinger at ca.afilias.info> 2012-08-07 10:05:02 PDT --- (In reply to comment #6) > (In reply to comment #5) > > Created an attachment (id=149) --> (http://www.slony.info/bugzilla/attachment.cgi?id=149) [details] [details] > > Updated bug272 patch > > > > This patch replaces the previous two. It also fixes an issue introduced in the > > previous patch parsing embedded quotes > > The patch does not check for possible NULL return of malloc()/realloc(). I > would also prefer comparing pointers to NULL instead of 0. What IS the proper thing to do from a lex/flex rule when a malloc fails? Call exit(1) ? Is there some way of aborting the scanning process? -- 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 258] cleanup thread can block waiting on a lock
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list