Re: ESQL 5.01UD1 core dumps.

In article 785@cbnewsh.cb.att.com, ijk@cbnewsh.cb.att.com (ihor.j.kinal) writes: > We're trying to upgrade some software that we can esql -e > with both 2.10 and 4.1 ESQL. It has numerous string * variables, > and several fetches. We can reduce the problem to > a simple fetch with one string * variable, and two long > host variables. If we DELETE this fetch, or change the > string * to an actual array, there is no core dump. > Unfortunately, it appears that the rest of the code somehow > affects the situtation, because if we strip out too much, > then the problem also goes away. > > The problem is that we can't debug the ESQLC core dumps. Since the code is > stripped, we can't do a stack back-trace. Our regency support > person claimed that the code does not give her a problem. > > We're running on HP 9000-870, HP UX 8.0. > > Any help will be appreciated, > Thanks, > Ihor Kinal > att!trumpet!ijk > The earlier versions of ESQL code will give core dump if you are passing pointers as host variables. There was a bug in ESQL preprocessed code it use to pass sizeof(host variable name) to the internal functions of informix, which will only be 4 for pointers. So the best soultion for you to do is change your host variables for character data type column to character arrays. This will work both in old and new version of ESQL preprocessor. I hope this will help you. shyam