Re: Trigger buffer problem causes lock-up

Main reason for asKing this is because Alan has noticed that the program is
hard coded to substring of 1087 byte out of the data buffer, which is a
dangerous thing to Do. It gets even more dangeraous when, as you have
mentioned, it is being used as a generic trigger.

I have two programs that acted differently after an OS upgrade/Recompile
(not sure which one). Both were caused by miss use of variable memory. One
of then declares a buffer that is longer than the length of the dataq. It
works for year util OS upgrade/recompile. The program starting to error out
when it calls the data queue api to get the data from dataq. The other is a
C program (enough say, I guess).




"James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx> wrote in message
news:mailman.8724.1256667209.1811.rpg400-l@xxxxxxxxxxxxxxx

hockchai Lim wrote:

You didn't happen to recompiled or upgraded you OS, did you?

It's the latest non-experimental version of the trigger program, compiled
only a week ago, but other than that, the conditions have not changed in
the slightest.

--
JHHL