Re: [q-lang-users] Suggestions on how to debug?

[Andrew B. <an...@vo...>]

Ok, I found the stack overflow that's been giving me troubles.  It is in =
clib.q, in the "regex" function.  Apparently this regex implementation =
breaks down when being used to split an 11k line file.

It looks to me like "regex_next" is doing all the work, and if asked to =
predict, I would guess that it is tail recursive.  I thought that my =
"EXPR" might be causing the trouble, so I tried:

=3D=3D> regex "g" "\n" H 1
! Stack overflow
>>> regex "g" "\n" H 1
                      ^

(H contains 1/2 MB of text in 11286 lines.)  I'm not sure exactly what =
to do from here.

-andrew

-----Original Message-----
From: Albert Graef

Andrew Berg wrote:
> =3D=3D> run fin.q
>=20
> =3D=3D> fetch_history "AA"
>=20
> C:\Documents and Settings\andrewb\Desktop\fin>
> ---------------------------------------------
>=20
> Maybe this example does not make it so obvious, but it
> appears to me that I am the victim of a silent
> failure.

Yes, I can confirm this, it also happens on Linux. It's a C stack
overflow in the interpreter's internal eval routine. We've discussed
this before, see:
 =
http://sourceforge.net/mailarchive/forum.php?thread_id=3D30658130&forum_i=
d=3D36790