Andy Gaynor <silver@mail.webspan.net> wrote:
+---------------
| > there is [or was] a debian package that contains elk
|
| It's there, I had Elk installed and didn't even know it.
+---------------
Well, then hopefully you won't need the following suggestions.
But just in case... ;-}
+---------------
| > The "INSTALL" file's instructions for customization are pretty easy to
| > follow, did you try them? There is an "i486-linux-gcc" in the "config" dir
|
| I played with it for a couple hours. ... More challenging is determining
| "the address of the faulting memory reference" for SIGSEGV and SIGBUS
+---------------
Recently I've been playing some with Elk, trying some experiments
with changing the object representation & GC [don't ask!], and have
run into my share of SIGSEGVs, too! ;-} ;-} Anyway, if you change
the compile flags to add "-g" (I did it in the "site" file), GDB
seems to work well enough, at least to let you know which file the
problem's in. To narrow it down to the exact failing operation, a
couple of times I had to recompile that source file without "-O"
(but this is not unusual).
-Rob
-----
Rob Warnock, 8L-855 rpw3@sgi.com
Applied Networking http://reality.sgi.com/rpw3/
Silicon Graphics, Inc. Phone: 650-933-1673
2011 N. Shoreline Blvd. FAX: 650-964-0811
Mountain View, CA 94043 PP-ASEL-IA