[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gdb on Alpha Tru64 UNIX 5.1A

From: Ken Raeburn
Subject: gdb on Alpha Tru64 UNIX 5.1A
Date: Tue, 23 Jul 2002 01:45:23 -0400

First bug:

Nowhere could I find any sort of "supported platforms" list for
gdb-5.2, so the only thing I could do is download, compile, install,
and try it.  If it's already known not to support this version of the
OS, or the native compiler, then I've wasted my time, and now I'm
wasting yours.

Second bug:

rsts-11.mit.edu> gdb src/temacs   
GNU gdb 5.2
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "alphaev67-dec-osf5.1"...Error reading symbol table: 
File truncated

This is a dynamically linked executable produced using the system
compiler and other tools, from a reasonably current CVS snapshot of
Emacs.  It's not the "dumped" version, so the Emacs unexec code isn't
to blame.  No warnings were produced at link time.

I would try confirming that the object file is intact using dbx, but
apparently I haven't got a license for it on the machine at the

Using "objdump -t" from binutils 2.12.1 also gets the "File truncated"
error.  The native "odump -t" seems quite happy with the file,
displaying almost 55000 symbol table entries.

I looked through gnu.gdb.bug on my local news server, and in the dozen
messages that weren't spam (out of over 700!), I did find one where
Andrew Cagney referred to some problem on Tru64 5.1A being fixed in
the current snapshots, though the description of the original problem
had expired.  So I downloaded gdb+dejagnu-20020723, and built it
(after deleting the dejagnu directory, which didn't configure because
I don't have a C++ compiler, because the gcc build blew out, but I'm
getting off topic), and it still reports the same problem.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]