gdb crashed with SIGSEGV in lookup_objfile_from_block()

Bug #1211412 reported by Muelli
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gdb (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I was debugging V8

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gdb 7.6~20130417-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Mon Aug 12 18:38:50 2013
ExecutablePath: /usr/bin/gdb
InstallationDate: Installed on 2013-06-25 (48 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: gdb --args out/x64.debug/cctest test-ast
SegvAnalysis:
 Segfault happened at: 0x5980cd <lookup_objfile_from_block+84>: mov 0x10(%rax),%rax
 PC (0x005980cd) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gdb
Stacktrace:
 #0 0x00000000005980cd in lookup_objfile_from_block ()
 No symbol table info available.
 Cannot access memory at address 0x7fff1f4ed258
StacktraceTop: lookup_objfile_from_block ()
ThreadStacktrace:
 .
 Thread 1 (LWP 1800):
 #0 0x00000000005980cd in lookup_objfile_from_block ()
 No symbol table info available.
 Cannot access memory at address 0x7fff1f4ed258
Title: gdb crashed with SIGSEGV in lookup_objfile_from_block()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

Revision history for this message
Muelli (ubuntu-bugs-auftrags-killer) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00000000005980cd in lookup_objfile_from_block (block=<error reading variable: Cannot access memory at address 0x7fff1f4ed238>, block@entry=<error reading variable: Cannot access memory at address 0x7fff1f4ed258>) at /build/buildd/gdb-7.6~20130417/gdb/symtab.c:1455
         obj = <error reading variable obj (Cannot access memory at address 0x7fff1f4ed240)>
         s = <error reading variable s (Cannot access memory at address 0x7fff1f4ed248)>
 Cannot access memory at address 0x7fff1f4ed258
StacktraceSource:
 #0 0x00000000005980cd in lookup_objfile_from_block (block=<error reading variable: Cannot access memory at address 0x7fff1f4ed238>, block@entry=<error reading variable: Cannot access memory at address 0x7fff1f4ed258>) at /build/buildd/gdb-7.6~20130417/gdb/symtab.c:1455
   [Error: /build/buildd/gdb-7.6~20130417/gdb/symtab.c was not found in source tree]
StacktraceTop: lookup_objfile_from_block (block=<error reading variable: Cannot access memory at address 0x7fff1f4ed238>, block@entry=<error reading variable: Cannot access memory at address 0x7fff1f4ed258>) at /build/buildd/gdb-7.6~20130417/gdb/symtab.c:1455

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gdb (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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
Matthias Klose (doko) wrote :

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel free to re-open the issue if the problem persists.

Changed in gdb (Ubuntu):
status: Confirmed → 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.