Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
spilker found c4gl 7.32.FC2 (server 9.40.FC3) segfaulted on RECORD LIKE for a table with LVARCHAR columns. scottishpoet said it is a known problem with arrays of records. Jonathan Leffler said I4GL does not support types newer than IDS 7.31, so the compiler should reject the program rather than crash, and a bug could be reported. scottishpoet saw a memory fault on 7.32.UC3.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Is this a known issue that i cannot use RECORD LIKE definitions for
tables containing lvchar type columns? Informix 4GL version used is
7.32.FC2 on server 9.40.FC3. c4gl crashes with segmentation fault in
this case.
spilker wrote:
> Is this a known issue that i cannot use RECORD LIKE definitions for
> tables containing lvchar type columns? Informix 4GL version used is
> 7.32.FC2 on server 9.40.FC3. c4gl crashes with segmentation fault in
> this case.
The crash is at best undesirable - but I would not expect I4GL to know
how to handle LVARCHAR. I'm not sure how meaningful it is to you, but
the rule of thumb is "if it isn't in IDS 7.31, I4GL probably won't
support it". (Unless there's a release note that says otherwise, that
would mean I4GL will not understand BOOLEAN, INT8, or SERIAL8 as well as
LVARCHAR(n).)
So, you could report a bug - the compiler should complain that it is an
unrecognized type, not core dump. But the most likely fix would be to
reject the program without core dumping, rather than to accept it.
Agitating for the bigger fix might eventually work, but I wouldn't hold
my breath while waiting. (I was briefly thinking that the I4GL code
could probably, just about, treat the LVARCHAR as a big CHAR type ...
except for the blank padding. If I4GL declared the host variable in the
generated ESQL/C as a string type - instead of char type - it would not
include trailing blanks.)
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.