dbx core dump

Hi,

We have an application successfully running in server1.

In bringing the same source to server2, we encountered core dump (with different configuration) using debugger. We can compile and execute the executable in server2 but we cannot step or trace the source using debugger.

We have try compiling and execute other programs with and without debugger and it works. So, we do not know how come this program cannot be executed in server2.

I hope to know the following:

1) Reason of the core dump (different workstation type, C++ 4.2 not compatible with SW 3.1, etc.)?

2) Way to overall this problem (any other methods to help us in identification problems)?

3) Before I upgrade server2 to SUN Workshop (dbx & debugger) Version 4.0/4.2, I need to confirm that it will solve the problem.

All help is appreciated.

The configuration of the two Solaris machines (server1 and server2) is as follows.

Server1

-

SUNOS Release 5.5.1

sun4u sparc SUNW,Ultra-2

SUN Workshop (dbx & debugger) Version 4.0

SUN CC Compiler 4.2

Server2

-

SUNOS Release 5.5.1

sun4u sparc SUNW, Ultra-1,

SUN Workshop (dbx & debugger) Version 3.1

SUN CC Compiler 4.2.

[1288 byte] By [johntrop] at [2007-11-25 23:40:56]
# 1

I am facing a somewhat similar symptom. dbx6.0 (SunOS5.6/purify4.5.1) will core dump when I say "run <arg1> <arg2>" at the prompt while tracing a purified-executable; dbx will NOT dump core if that executable is not purify'd. The message I get is:

dbx: internal error: signal SIGSEGV (no mapping at fault address)

dbx's core dump will appear in </vol03/kiran/tmp>

Abort(coredump)

kirannmehta at 2007-7-5 18:48:40 > top of Java-index,Development Tools,Solaris and Linux Development Tools...