AFAICT tsearch2's incompatibility is in the redefined YY_INPUT macro,
which seems of no value for Postgres anyway.  Can't we take that out?

I resolve problem with gm4 with a help of symlink and reorder my PATH. So, it compiles but creates core dump while regression (postgres is compiled with enable-debug and enable-cassert):


#0  0x284b5507 in tsearch2_yy_switch_to_buffer (new_buffer=0x84040a0)
    at parser.c:1725
1725                    YY_CURRENT_BUFFER_LVALUE->yy_buf_pos = (yy_c_buf_p);
(gdb)  print (yy_buffer_stack)[(yy_buffer_stack_top)]
$1 = 0x7f7f7f7f
(gdb)  print yy_buffer_stack_top
$2 = 0
(gdb) bt
#0  0x284b5507 in tsearch2_yy_switch_to_buffer (new_buffer=0x84040a0)
    at parser.c:1725
#1  0x284b5bb2 in tsearch2_yy_scan_buffer (
    base=0x8404314 "345 [EMAIL PROTECTED] ' http://www.com/ 
http://aew.werc.ewr/?ad=qwe&;
dw 1aew.werc.ewr/?ad=qwe&dw 2aew.werc.ewr http://3aew.werc.ewr/?ad=qwe&dw http:/
/4aew.werc.ewr http://5aew.werc.ewr:8100/?  ad=qwe&dw 6aew.w"..., size=566)
    at parser.c:1976
#2  0x284b5c8e in tsearch2_yy_scan_bytes (
    bytes=0x835aa48 "345 [EMAIL PROTECTED] ' http://www.com/ 
http://aew.werc.ewr/?ad=qwe
&dw 1aew.werc.ewr/?ad=qwe&dw 2aew.werc.ewr http://3aew.werc.ewr/?ad=qwe&dw http:
//4aew.werc.ewr http://5aew.werc.ewr:8100/?  ad=qwe&dw 6aew.w"..., len=564)
    at parser.c:2020
#3  0x284b5fed in start_parse_str (
    str=0x835aa48 "345 [EMAIL PROTECTED] ' http://www.com/ 
http://aew.werc.ewr/?ad=qwe&d
w 1aew.werc.ewr/?ad=qwe&dw 2aew.werc.ewr http://3aew.werc.ewr/?ad=qwe&dw http://
4aew.werc.ewr http://5aew.werc.ewr:8100/?  ad=qwe&dw 6aew.w"..., limit=564)
    at parser.l:303

It seems to me, bug in flex...






-- Teodor Sigaev E-mail: [EMAIL PROTECTED]


---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

Reply via email to