solaris memory concerns

I am porting a c-code based accounting package onto a solaris machine, but I have been having difficulty with memory on the machine.  The current version of the source code runs on a SCO system with no problems.

The program performs core dumps during the running of the program with errors like SIGBUS error or SIGSEGV error.

One of the core dumps stops at a line in the code that reads: = + ilfb.P->blank,

where is a pointer into memory, is also a pointer into memory,
and ilfb.P->blank is an offset factored into

Any reason as to why this simple command core dumps?  Other core dumps have occurred in memory to memory transfers, such as:

strcpy(address1, address2);

Are there memory concerns in solaris that are not true of other unix OS's?

Thanks in advance.
Who is Participating?
roy020697Connect With a Mentor Commented:
I don't think it is a memory issue; more likely it is a portability issue. You should set the warning severity of your compiler way up to complain about everything, then examine the suspicious code which generated warnings from the compiler. Make sure the libraries you need to link with are specified in the right order.

I'm afraid that is as specific an anser I can give with the information you've given me. Your code snippet is legal (but not very portable).  :-(
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.