touch-packages team mailing list archive

[Matthias Klose <doko@xxxxxxxxxx>]

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?


** Information type changed from Private to Public

** Changed in: gdb (Ubuntu)
       Status: New => Invalid

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

Title:
  gdb crashed with SIGABRT in command_line_input()

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  updating process from oneiric to pricise

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gdb 7.4-2012.02-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  Date: Mon Apr  2 12:30:17 2012
  Disassembly: => 0x7f0535d6f445:	Cannot access memory at address 0x7f0535d6f445
  ExecutablePath: /usr/bin/gdb
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  ProcCmdline: gdb --batch --ex file\ /usr/sbin/cron --ex core-file\ /tmp/tmpa4kWgu --ex set\ backtrace\ limit\ 2000 --ex p\ -99 --ex bt\ full --ex p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex info\ registers --ex p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex print\ (char*)\ __abort_msg
  ProcEnviron:
   PATH=(custom, user)
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gdb
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   command_line_input ()
  Title: gdb crashed with SIGABRT in command_line_input()
  UpgradeStatus: Upgraded to precise on 2012-04-02 (0 days ago)
  UserGroups:

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