touch-packages team mailing list archive

[Harald Sitter <sitter.harald@xxxxxxxxx>]

Public bug reported:

GDB 7.8 has a broken --batch functionality. In batch mode gdb is not
able to fetch a proper backtrace and instead prints two garbled frames
that have nothing to do with the actual process (always two apparently).
It works perfectly fine when one runs gdb without batch and runs the
exactly same commands.

This breaks all KDE software backtracing/crash bug reporting!

# How to reproduce
echo "thread apply all bt" > /tmp/instr
gdb --batch -x /tmp/instr -p `pidof kate` /usr/bin/kate

|
|
v

Thread 1 (process 23159):
#0  0x00007ff7ffafb39d in ?? ()
#1  0x0000000000000000 in ?? ()

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


** Tags: kubuntu

-- 
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/1371043

Title:
  gdb --batch broken since 7.8

Status in “gdb” package in Ubuntu:
  New

Bug description:
  GDB 7.8 has a broken --batch functionality. In batch mode gdb is not
  able to fetch a proper backtrace and instead prints two garbled frames
  that have nothing to do with the actual process (always two
  apparently). It works perfectly fine when one runs gdb without batch
  and runs the exactly same commands.

  This breaks all KDE software backtracing/crash bug reporting!

  # How to reproduce
  echo "thread apply all bt" > /tmp/instr
  gdb --batch -x /tmp/instr -p `pidof kate` /usr/bin/kate

  |
  |
  v

  Thread 1 (process 23159):
  #0  0x00007ff7ffafb39d in ?? ()
  #1  0x0000000000000000 in ?? ()

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