4GL V7.32 issue

[Malc P]

OK, testing i4GL V7.32 on HP-UX 11i, IDS9.40.
The following code is coredumping:
(this is a cut down version of a bigger file, to the point where this
is the minimum to replicate the coredump)

################################################## #########################
database active

FUNCTION default_de_bond1()
DEFINE mr_de_bond1 RECORD LIKE de_bond1.*

SELECT *
INTO mr_de_bond1.*
FROM de_bond1

END FUNCTION
################################################## #########################

the schema for table de_bond1 has 258 columns, total width 3881 bytes.
Mostly chars, dates and integers - no special columns (byte, text
etc). Similar functions using other tables from the database are ok.
Is this error caused by the number of columns or rowsize in the table?
No info in release notes to suggest this.
The code compiles OK with r4gl, and the .err file produced by i4gl is
0 bytes.

Schema header:
{ TABLE "dba".de_bond1 row size = 3881 number of columns = 258 index
size = 100
}

Thanks for any help
--
Malc_p

[Mark D. Stock]

Venkatesh Gopal wrote:

>
> There is a bug associated with this in 4GL , and will be fixed in the new
> release.
>
> Venkatesh.
>
> Malc_p wrote:
>
>

>>OK, testing i4GL V7.32 on HP-UX 11i, IDS9.40.
>>The following code is coredumping:
>>(this is a cut down version of a bigger file, to the point where this is

>
> the minimum to replicate the coredump)
>

>>

>

################################################## #########################

>

>>database active
>>
>>FUNCTION default_de_bond1()
>>DEFINE mr_de_bond1 RECORD LIKE de_bond1.*
>>
>> SELECT *
>> INTO mr_de_bond1.*
>> FROM de_bond1
>>
>>END FUNCTION
>>

>
>

################################################## #########################

>

>>the schema for table de_bond1 has 258 columns, total width 3881 bytes.

>
> Mostly chars, dates and integers - no special columns (byte, text etc).
> Similar functions using other tables from the database are ok. Is this
> error caused by the number of columns or rowsize in the table? No info in
> release notes to suggest this.
>

>>The code compiles OK with r4gl, and the .err file produced by i4gl is 0

>
> bytes.
>

>>Schema header:
>>{ TABLE "dba".de_bond1 row size = 3881 number of columns = 258 index size

>
> = 100
>

>>}

>
>
> That is a MONSTER table! From your code I would expect this to be a
> memory allocation problem. Have you tried explicitly defining the record
> elements instead of using the LIKE keyword? (Cut&Paste is your friend
> there. ;-)
>
> Cheers,
> --
> Mark.

Cheers,
--
Mark.

+----------------------------------------------------------+-----------+
| Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// /|
| Mydas Solutions Ltd [url]http://MydasSolutions.com[/url] |///// / //|
| +-----------------------------------+//// / ///|
| |We value your comments, which have |/// / ////|
| |been recorded and automatically |// / /////|
| |emailed back to us for our records.|/ ////////|
+----------------------+-----------------------------------+-----------+

sending to informix-list