So it's yyparse itself that segfaults and you don't get any useful line number info in it?
/ Martin Stjernholm, Roxen IS
Previous text:
2003-01-09 12:28: Subject: --with-machine-code continued
With COMPILE_DEBUG:
| % ./pike -m master.pike . . . | th(0) start_new_program(64, /home/mirar/Pike7.5-20030109-040008/src/module.c): threads_disabled:0, compilation_depth:0 | th(0) 0x83afec8 low_start_new_program() - pass=1: threads_disabled:0, compilation_depth:1 | th(0) 0x83afec8 end_first_pass(1): threads_disabled:0, compilation_depth:1 | th(0) 0x83b2160 end_first_pass(1): threads_disabled:0, compilation_depth:0
(init_modules ends here)
| th(0) (nil) compile() enter, placeholder=(nil) | th(0) 0x83afdf0 low_start_new_program() - pass=0: threads_disabled:0, compilation_depth:0 | th(0) 0x83afdf0 run_pass1() start: threads_disabled:0, compilation_depth:0
(yyparse is called here)
| Segmentation fault (core dumped)
Any way to debug/trace yyparse?
/ Mirar