Re: [zile-devel] problems with zile

[Reuben Thomas]

I'm afraid the backtrace doesn't make a lot of sense.

> Program received signal SIGSEGV, Segmentation fault.
> 0x400dbc2f in strlen () from /lib/libc.so.6
> (gdb) bt
> #0  0x400dbc2f in strlen () from /lib/libc.so.6
> #1  0xbffff918 in ?? ()
> #2  0x0805a015 in tgetstr_note_len (cap=0x0, tcap=0x0) at term_termcap.c:267

If this really was called from line 311 (as below) then neither cap nor 
tcap should be NULL (in particular, cap is a literal string!).

> #3  0x0805a187 in term_init () at term_termcap.c:311
> #4  0x08054af0 in main (argc=0, argv=0x0) at main.c:368

Again, how can argv possibly be NULL?

Even if there is memory corruption going on, I don't see how cap can be 
overwritten between #3 (line 311) and #2 (line 267).

Sorry, I don't understand this...I'll do a complete rebuild of my tree 
later and see if I can repro anything like this. Did you try running 
under valgrind? If there is memory corruption it will catch it earlier.

--
http://rrt.sc3d.org/ | free, a.  already paid for (Peyton Jones)