help on non-existing entry segfaults

[Dmitri A. Sergatskov]

help junk111

(or some other non-existing entry)
causes octave to "hang" for a couple minutes and then die
with a seg. fault.
Sometimes it happens with existing entries as well, but not as
reproducible. That happens with both 3.2.4 and 3.3.51.
I tried to run through strace and it produced a 150MB log
file. The tail looks like that:

 stat("/usr/local/share/octave/site/m", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
stat("/usr/local/share/octave/site/m/startup", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
stat("/usr/local/libexec/octave/3.3.51/oct/x86_64-unknown-linux-gnu",
{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat("/usr/local/share/octave/3.3.51/m", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV (core dumped) +++

This is with self-compiled octave-3.3.51 on Fedora 13 (x86_64).
Anyone see the same?

Sincerely,

Dmitri.
--