This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gdb/873: Solaris 8 64-bit mode dumps SunOS programs in a format gdb can't read


>Number:         873
>Category:       gdb
>Synopsis:       Solaris 8 64-bit mode dumps SunOS programs in a format gdb can't read
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 06 02:38:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     joelsaacks@hotmail.com
>Release:        gdb 5.21
>Organization:
>Environment:
Solaris 8 - 64 bit mode - SunOS BCP application.
>Description:
I'm in the process of converting my system from a gcc one compiled on a Sparc 5 ( SunOS ) to Forte C++.
But in the interim, the original system is running on a SunBlade 100 running Solaris 8 in 64-bit mode using BCP.

The program occasionally core dumps, but GDB can't read the core file. It reports its not a core dump file - no such file or directory.

The program, when it dumps core on Solaris 2.51, creates a core file gdb can read perfectly.

On Solaris 8, gdb 5.21 can read the executable perfectly, but doesn't understand any core dumps it creates.

I wrote a simple C program on the SunOS box, which will dump a core file, On all boxes, but the Solaris 8-64 bit one, is the core file readable. 

the program looks like:

char * empty;
char bigarray[255];
main()
{
  memcpy( empty, &igarray, sizeof( bigarray ));
}

This generates a segmentation core dump.

If necessary, I can email the core file to you, but its large.
>How-To-Repeat:
see details.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]