From: Sam S. <sd...@gn...> - 2000-12-14 21:44:13
|
> * In message <149...@ho...> > * On the subject of "Re: segfault" > * Sent on Thu, 14 Dec 2000 19:01:44 +0100 (CET) > * Honorable Bruno Haible <ha...@il...> writes: > > Sam writes: > > How do I debug a segfault? > > Somehow the memory is corrupted and I get random segfaults. > > Ouch. This is hard. I'd try to insert many (gc) calls in order to get > an idea which function corrupts memory. Bruno, thanks a bundle!!! I suggest this in lispbibl.d (so that I won't have to reinvent the wheel every time I have a fault): #define CHECK_MEM(msg) do { printf msg; gar_col(); } while(0) > Once you got it located, proofread the suspicious code. the bad news is that the "suspicious code" is the innocently looking call to allocate_dir_key()! Bruno, do you mind looking at lispbibl.d? -- Sam Steingold (http://www.podval.org/~sds) Support Israel's right to defend herself! <http://www.i-charity.com/go/israel> Read what the Arab leaders say to their people on <http://www.memri.org/> The difference between genius and stupidity is that genius has its limits. |