Re: [lkb] Getting Parse results from LKB
Bernhard Fisseni <[email protected]> Mon, 16 Oct 2006 23:04:52 +0200
| Newsgroups | gmane.comp.ai.lkb |
|---|---|
| Organization | Institut für Kommunikationswissenschaf ten – Abteilung Sprache und Komunikation –, Rheinische Friedrich-Wilhelms-Universität Bon n |
| Message-ID | <[email protected]> |
Scripsit Ann Copestake di=C4=93 16.10.2006 21:52: > [email protected] said: >> Thanks, it seems it loads in sbcl now ("test" version, not "latest") =C3= =A2=E2=82=AC=E2=80=9C some >> success! And I suppose, the memory issue is responsible for the foll= owing >> message I get when I try to load GG or ERG? >=20 >> fatal error encountered in SBCL pid 1117: >> fake_foreign_call fell through >=20 > I don't know, but that's not the error Ben reported, which was >=20 >> Argh! gc_find_freeish_pages failed (restart_page), nbytes=3D4456456. >=20 > The SBCL discussion is all on the developers list - e.g.,=20 > http://lists.delph-in.net/archive/developers/2006/000566.html > I don't have any other info since I haven't tried it I'll have a look at that tomorrow, thanks for the pointer! > Actually I'd be worried that that the error you have is due to somethin= g else=20 > - have you tried on a smaller grammar? you might also have to have an = up to=20 (read-script-file-aux "lkb/src/data/esslli2k/grammars/grammar9/script") works. So it might be some kind of memory problem. Under Linux (under=20 Parallels, 1 of the 1.5 GB on the Mac; no bigger memory in sight), I get=20 a heap exhaustion for ERG; maybe the fake_foreign_call is a Mac OS proble= m? > date version of the ERG / GG. If it isn't the memory problem, you migh= t want=20 > to email the developers list with a trace - it's probably better to hav= e the=20 > discussion there than on lkb. or you can email me and I'll forward it. I don't get a real trace; the script stops with [...] Reading preprocessor rules `rondane.fsr' fatal error encountered in SBCL pid 652: fake_foreign_call fell through LDB monitor ldb> Is there any way to produce something more useful? (Posting this short=20 message to the developers' list will only amuse people, won't it?) Thanks, Bernhard