roxen.lists.roxen.general

Subject Author Date
Re: Roxen 4.0 sudden death on piketag - corrupted double-linked lists on #include? <gnudiff <> 05-01-2006
2006/1/5, Martin Bähr <<mbaehr[at]email.archlab.tuwien.ac.at>>:
> > If I insert the contents of the .h file in the RXML file, and remove
> > #include, everything works as expected.
>
> so it's not the contents of the file after all.
> can you reproduce the problem with a different pike tag that just
> #includes some simple stuff?
>
> greetings, martin.

Now I have "fixed" the previous file, I am starting to have the exact
same problem in another piketag in a different location, which does
NOT have #include anywhere in it. :(

The things that those files share in common is:
- db interaction (postgres) via Sql.Sql() /1script/ and/or
DBManager.get() /other/;
-- DB itself is ok, as the RXML <emit> and <sqlquery> tags work all the time.

- regexp usage for checking validity                 object(Regexp)
validchars = Regexp("^[A-Za-z0-9\.,_=@]([
A-Za-z0-9\.,_=@])*[A-Za-z0-9\.,_=@]$");

- RXML variable usage within piketag for passing info to piketag and
back to the RXML file, like:  form.myvar1 and var.myvar2 in
assignments and


The problem appears to be in Roxen itself tho or hardware, as I
managed to catch a console error message:

*** glibc detected *** malloc(): memory corruption (fast):
0x00000000010c524e ***

and this other piketag now exits simply at:

    <?pike

                array(string) errors = ({ });
                write("TEST OK");
                return;

....
?>