← Back to team overview

touch-packages team mailing list archive

[Bug 1361973] [NEW] Got object file from memory but can't read symbols: File truncated.

 

Public bug reported:

A number of our binaries cause this message from gdb when I run under
gdb:

    $ gdb ./Reaper_test 
    GNU gdb (Ubuntu 7.8-0ubuntu1) 7.8
    ...
    Reading symbols from ./Reaper_test...done.
    (gdb) run
    Starting program: /home/michi/src/fix-reaper-test/build/test/gtest/scopes/internal/Reaper/Reaper_test 
    Got object file from memory but can't read symbols: File truncated.

At that point, gdb consumes 100% and does not respond to SIGINT,
SIGQUIT, or anything other than SIGKILL, as far as I can tell.

It turns out that, after waiting a looong time (as in around 85
seconds), gdb recovers and appears to run the code normally. Neither the
error message nor the long wait are nice.

To reproduce, grab lp:~michihenning/unity-scopes-api/fix-reaper-test and
check out revision 474.

Build the project:

$ mkdir build
$ cd build
$ cmake -DCMAKE_BUILD_TYPE=debug ..
$ cd test/gtest/scopes/internal/Reaper
$ gdb ./Reaper_test

** Affects: gdb (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1361973

Title:
  Got object file from memory but can't read symbols: File truncated.

Status in “gdb” package in Ubuntu:
  New

Bug description:
  A number of our binaries cause this message from gdb when I run under
  gdb:

      $ gdb ./Reaper_test 
      GNU gdb (Ubuntu 7.8-0ubuntu1) 7.8
      ...
      Reading symbols from ./Reaper_test...done.
      (gdb) run
      Starting program: /home/michi/src/fix-reaper-test/build/test/gtest/scopes/internal/Reaper/Reaper_test 
      Got object file from memory but can't read symbols: File truncated.

  At that point, gdb consumes 100% and does not respond to SIGINT,
  SIGQUIT, or anything other than SIGKILL, as far as I can tell.

  It turns out that, after waiting a looong time (as in around 85
  seconds), gdb recovers and appears to run the code normally. Neither
  the error message nor the long wait are nice.

  To reproduce, grab lp:~michihenning/unity-scopes-api/fix-reaper-test
  and check out revision 474.

  Build the project:

  $ mkdir build
  $ cd build
  $ cmake -DCMAKE_BUILD_TYPE=debug ..
  $ cd test/gtest/scopes/internal/Reaper
  $ gdb ./Reaper_test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1361973/+subscriptions


Follow ups

References