gdb message "Got object file from memory but can't read symbols: File truncated."

Bug #1348275 reported by James Hunt
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Python
Invalid
Unknown
gdb (Ubuntu)
Fix Released
High
Unassigned
Utopic
Won't Fix
High
Unassigned

Bug Description

Test Case
---------
$ cat >>foo.c<<EOT
#include <stdio.h>
#include <stdlib.h>

int
main (int argc, char *argv[])
{
    printf ("hello world\n");
    exit (EXIT_SUCCESS);
}
EOT
$ gcc -ggdb -O0 foo.c
$ ./a.out
hello world
$ gdb ./a.out
GNU gdb (Ubuntu 7.7.91.20140723-0ubuntu1) 7.7.91.20140723-cvs
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./a.out...done.
(gdb) r
Starting program: /tmp/a.out
Got object file from memory but can't read symbols: File truncated. # XXX: <<< What is this? XXX:
hello world
[Inferior 1 (process 21518) exited normally]
(gdb)

ProblemType: BugDistroRelease: Ubuntu 14.10
Package: gdb 7.7.91.20140723-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
Uname: Linux 3.16.0-5-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul 24 17:55:11 2014
InstallationDate: Installed on 2014-04-11 (103 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)SourcePackage: gdb
UpgradeStatus: Upgraded to utopic on 2014-05-08 (77 days ago)

Revision history for this message
James Hunt (jamesodhunt) wrote :
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gdb (Ubuntu):
status: New → Confirmed
Revision history for this message
Barry Warsaw (barry) wrote :

This is likely the cause of the upstream Python test suite failures.

Changed in python:
status: Unknown → New
Revision history for this message
Jan Kratochvil (jan-kratochvil) wrote :
Changed in gdb (Ubuntu):
importance: Undecided → High
Matthias Klose (doko)
Changed in gdb (Ubuntu Utopic):
importance: Undecided → High
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gdb - 7.8.1-1ubuntu1

---------------
gdb (7.8.1-1ubuntu1) vivid; urgency=medium

  * Merge with Debian; remaining changes:
    - Build from the upstream sources.
    - Build the gdb-doc package.
    - Include the man pages in the gdb package.
    - Build-depend on gcj-jdk.
    - Drop build dependency on python-dev.
    - Additional patches branch-updates, gdb-strings, ptrace-error-verbosity,
      ppc64el-gdbserver, ppc64el-attach-jvm.
    - Don't build a gdb-python2 package.
    - Configure with babeltrace on ppc64 and ppc64el.
    - gdb: Add a replaces to gdb-doc, which used to ship the manual pages.
    - Again, stop building the gdb-minimal package, not used anymore on any
      image.
    - Add build dependencies for the gdb-doc package.
    - Make gdb Multi-Arch: allowed again.
  * Upstream fixes LP: #1348275.

gdb (7.8.1-1) experimental; urgency=medium

  * Imported Upstream version 7.8.1
    - GDB 7.8.1 provides the following fixes and improvements over GDB 7.8:
      + PR python/17364 (Need better printer names in bound_registers.py)
      + PR build/17104 (CFLAGS="-Wall -Wextra" gdb/confgure --with-babeltrace
        fails)
      + PR gdb/17345 (babeltrace (1.1.2 and later) complains about the ctf
        data generated by GDB)
      + PR build/17298 (gcore: Couldn't get registers: No such process)
      + PR python/17342 (Xmethod Python is not Python 3 compatible)
      + PR python/17355 (Crash on Python frame filters with unreadable arg)
      + PR guile/17367 (computation of guild path wrong when pkg-config script
        supplied as arg to --with-guile)
      + PR gdb/17247 (gdb freezes on multi threaded app)
      + PR gdb/17347 (Regression: GDB stopped on run with attached process)
      + PR gdb/17407 (Regression for Linux vDSO reading)
      + PR server/17457 (aarch64/gdbserver: wrong floating point registers
        display)
      + PR server/17487 (state->dr_control_mirror == 0 failed assertion in
        gdbserver on Windows)
      + PR gdb/17472 (with annotations, input while executing in the foreground
        crashes readline/gdb)
      + PR gdb/17471 (repeating a background command makes it foreground)
      + PR cli/17300 (crash in non-stop mode with continue -a &
        (readline_callback_read_char() called with no handler!))
      + PR python/17372 (python hangs when displaying help())
      + PR python/17408 (../../gdb/infrun.c:5256: internal-error:
        switch_back_to_stepped_thread: Assertion `!schedlock_applies(1)'
        failed.)
    - Fix --batch mode parameter
      (Closes: #763518)
  * d/control*:
    - Bump Standars Version stanza, no changes needed.
    - -dbg depends on main binary version.
  * d/rules: fix FTBFS caused by dpkg 1.17.17 changes.
    (Closes: #766754)
 -- Matthias Klose <email address hidden> Thu, 20 Nov 2014 09:28:37 +0100

Changed in gdb (Ubuntu):
status: Confirmed → Fix Released
description: updated
Revision history for this message
Rolf Leggewie (r0lf) wrote :

utopic has seen the end of its life and is no longer receiving any updates. Marking the utopic task for this ticket as "Won't Fix".

Changed in gdb (Ubuntu Utopic):
status: In Progress → Won't Fix
Changed in python:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.