Problems running GDB-5.1.

Problems running GDB-5.1.

[Trant, Bert]

I built, w/o any problems, GDB-5.1 on a Tru64 Unix 4.0F XP900 EV6 system.

When I try and look at a core file using:

	gdb -core core

I recieve the following warning message:
	
	warning: big endian file does not match little endian target.

I am running this on a little endian architecture and I have 

	set endian auto (currently set to little endian).

In fact, AUTO seems to be the only valid setting for ENDIAN as I am not able
to set it to big or little exclusively.

I do not know if this warning message will cause the debugging information
to be unreliable as I do not know the exact meaning of this message.

Any info on this would be greatly appreciated.

						Thanks in Advance,
						Bert Trant
						bert.trant@csoconline.com

Re: Problems running GDB-5.1.

[Joel Brobecker]

> I recieve the following warning message:
> 	
> 	warning: big endian file does not match little endian target.

Did you compile GDB with GCC or the Tru64 C compiler? If you compiled
with GCC, you may have run into the same problem as I did. I fixed it
by compiling with -D__digital__:

     make CC=gcc CFLAGS="-O2 -D__digital__"

What happens is that GCC picks up the wrong definitions for the
structure of the core file if this macro is not defined. So the layout
of the data does not match and we end up reading some garbage. Hence
the bizarre messages.

-- 
Joel

Re: Problems running GDB-5.1.

[Andrew Cagney]

>> I recieve the following warning message:
>> 	
>> 	warning: big endian file does not match little endian target.
> 
> 
> Did you compile GDB with GCC or the Tru64 C compiler? If you compiled
> with GCC, you may have run into the same problem as I did. I fixed it
> by compiling with -D__digital__:
> 
>      make CC=gcc CFLAGS="-O2 -D__digital__"
> 
> What happens is that GCC picks up the wrong definitions for the
> structure of the core file if this macro is not defined. So the layout
> of the data does not match and we end up reading some garbage. Hence
> the bizarre messages.

Suggest a bug report and addition to the [5.3] gdb/PROBLEMS file.
The fix involves changing the configury.

Andrew

Re: Problems running GDB-5.1.

[Joel Brobecker]

[-- Attachment #1: Type: text/plain, Size: 407 bytes --]

> Suggest a bug report and addition to the [5.3] gdb/PROBLEMS file.
> The fix involves changing the configury.

Done: gdb/816.

I committed the following change to gdb/PROBLEMS in the 5.3 branch.
Should I do the same in the main trunk too, or is gdb/816 enough
for now?

2002-11-06  Joel Brobecker  <brobecker@gnat.com>

      * PROBLEMS: Document gdb/816 (unable to read core file on alpha-osf).

-- 
Joel

[-- Attachment #2: PROBLEMS.diff --]
[-- Type: text/plain, Size: 1039 bytes --]

Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.8
diff -c -3 -p -r1.8 PROBLEMS
*** PROBLEMS	24 Aug 2002 14:36:12 -0000	1.8
--- PROBLEMS	7 Nov 2002 07:14:29 -0000
*************** i386-*-freebsd4.4*
*** 50,52 ****
--- 50,67 ----
  
  gdb/455: GDB doesn't build on a FreeBSD 4.4-STABLE system.  The
  problem is still being investigated.
+ 
+ alpha*-*-osf*
+ -------------
+ 
+ gdb/816: When building GDB with GCC 3.0.1, GDB is unable to load a core
+ file properly. It generates several errors and warnings regarding
+ unhandled core file section types, incorrect endianness, the failure to
+ load the registers. Are also incorrectly reported: The program name, the
+ cause of the program death, and the call stack at the moment of the
+ death. This problem has been reported on alpha-osf4.0f and alpha-osf5.1a.
+ To work-around the problem, add -D__digital__ to the CFLAGS when
+ building GDB vis:
+ 
+     $ make CFLAGS='-O2 -D__digital__'
+ 

Re: Problems running GDB-5.1.

[Andrew Cagney]

> 
> Done: gdb/816.
> 
> I committed the following change to gdb/PROBLEMS in the 5.3 branch.
> Should I do the same in the main trunk too, or is gdb/816 enough
> for now?
> 
> 2002-11-06  Joel Brobecker  <brobecker@gnat.com>
> 
>       * PROBLEMS: Document gdb/816 (unable to read core file on alpha-osf).
> 
Can you do both?

The release process mentions re-syncing the two files just after a 
release, but then I might forget :-)

thanks!
Andrew

Re: Problems running GDB-5.1.

[Joel Brobecker]

> >2002-11-06  Joel Brobecker  <brobecker@gnat.com>
> >
> >      * PROBLEMS: Document gdb/816 (unable to read core file on alpha-osf).
> >
> Can you do both?
> 
> The release process mentions re-syncing the two files just after a 
> release, but then I might forget :-)

Sure! Done.

-- 
Joel