RE: memory fault, core dump

Thanks, we did what you suggested and got the following message Assertion failed: current_dll < num_dlls, file dll.c, line 335 bort(coredump) Any ideas? Dee Wampler Technical Leader > -----Original Message----- > From: Madison Pruet [SMTP:mpruet@home.com] > Sent: Monday, May 15, 2000 4:00 PM > To: informix-list@iiug.org > Subject: Re: memory fault, core dump > > Dee, > > I am not that familar with SCO. You might want to check to see if they > have > anything similar to the solaris truss. On some machines this would be > trace. > Basically what this does is to display all of the system calls made by the > executable. Chances are that you have a mismatch between some of the > shared > objects in your system and that is causing boundry problems (i.e. stuff > that is > supposed to be on a word boundry is on a half word). By examining the > output > of a truss-like utility, you can see exactly what shared library objects > were > loaded by the executable. > > "Wampler, Dee" wrote: > > > We have upgraded to INFORMIX-4GL Version 7.30.UC1X2 > > > > We added in one global variable (smallint) to an existing program, > compiled > > using -shared, and it ran fine > > Then we set the variable = 0 and got the following error > > dynamic linker: program name: invalid relocation type 72 at 0X0 > > killed > > > > If any other code is added, we get a memory fault core dump > > > > If we recompile with all the code, using -static, the problem goes away > and > > the program runs fine > > > > Any ideas? > > > > Dee Wampler > > Technical Leader

No, but this might be enough to get the SCO support to help you out. "Wampler, Dee" wrote: > Thanks, we did what you suggested and got the following message > Assertion failed: current_dll < num_dlls, file dll.c, line 335 > bort(coredump) > Any ideas? > > Dee Wampler > Technical Leader > > > -----Original Message----- > > From: Madison Pruet [SMTP:mpruet@home.com] > > Sent: Monday, May 15, 2000 4:00 PM > > To: informix-list@iiug.org > > Subject: Re: memory fault, core dump > > > > Dee, > > > > I am not that familar with SCO. You might want to check to see if they > > have > > anything similar to the solaris truss. On some machines this would be > > trace. > > Basically what this does is to display all of the system calls made by the > > executable. Chances are that you have a mismatch between some of the > > shared > > objects in your system and that is causing boundry problems (i.e. stuff > > that is > > supposed to be on a word boundry is on a half word). By examining the > > output > > of a truss-like utility, you can see exactly what shared library objects > > were > > loaded by the executable. > > > > "Wampler, Dee" wrote: > > > > > We have upgraded to INFORMIX-4GL Version 7.30.UC1X2 > > > > > > We added in one global variable (smallint) to an existing program, > > compiled > > > using -shared, and it ran fine > > > Then we set the variable = 0 and got the following error > > > dynamic linker: program name: invalid relocation type 72 at 0X0 > > > killed > > > > > > If any other code is added, we get a memory fault core dump > > > > > > If we recompile with all the code, using -static, the problem goes away > > and > > > the program runs fine > > > > > > Any ideas? > > > > > > Dee Wampler > > > Technical Leader