Solaris

any ideas on how to fix this achenle???, am no solaris tech your talking in a 9th language to me lol

He edited the first post completely changing the character of his problem.

all i did was update the log to show the full content that was all it is same error

More likely this program is trying to access somebody else's memory at 0x201138F4. Use mdb or dbx to see is actually going on in the code.

Is this code you wrote yourself or obtained from somewhere?

its a 3rd party program

Been offline for a while, sorry about the delay in responding.

First, make sure the installed software is correct. The mmap() of the actual binary read/write could have corrupted your installed copy, and caused the SIGILLs referred to in the thread. I can't tell you how to verify that since I don't know how it gets installed. You may need to do a reinstall. I will say, though, that merely checking file sizes isn't sufficient - you want to check actual contents of executable binary files since that mmap() listed in the truss output could easily corrupt the binary executable without changing the file size. (FWIW, that seems to me like the process is open()'ing and mmap()'ing the wrong file.)

After that? I'd thoroughly verify that the product is being used properly. Check the command line arguments carefully.

Without more detailed knowledge of the product, I can't give more specific help.