rasmol.32 crashed with SIGSEGV in XCopyArea()

Bug #915228 reported by Sasa Paporovic
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
RasMol
New
Undecided
Unassigned
rasmol (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have just started the classic version of RasMol on Ubuntu12.04 64bit updated to 12.1.2012.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rasmol 2.7.5-3
ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Jan 12 10:46:37 2012
ExecutablePath: /usr/lib/rasmol/rasmol.32
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/rasmol/rasmol.32
SegvAnalysis:
 Segfault happened at: 0x7fe25e6876a2 <XCopyArea+66>: cmpq $0x0,0x18(%r13)
 PC (0x7fe25e6876a2) ok
 source "$0x0" ok
 destination "0x18(%r13)" (0x00000018) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rasmol
StacktraceTop:
 XCopyArea () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: rasmol.32 crashed with SIGSEGV in XCopyArea()
UpgradeStatus: Upgraded to precise on 2011-12-31 (11 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare

Revision history for this message
Sasa Paporovic (melchiaros) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XCopyArea (dpy=0xfc7010, src_drawable=0, dst_drawable=0, gc=0x0, src_x=0, src_y=0, width=16, height=16, dst_x=-64, dst_y=0) at ../../src/CopyArea.c:49
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

I get the same segfault when attempting to start rasmol-classic. Note that it doesn't seem to affect rasmol nor rasmol-gtk.

Changed in rasmol (Ubuntu):
status: New → Confirmed
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Seen on quantal. I add the tag for.

tags: added: quantal
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

This also happends with the gtk version

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

The upstream report could be found at:

https://sourceforge.net/p/openrasmol/bugs/10/

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

hjd,

may be it makes sense to leafe a comment on the upstream tracker.

You know more noise generate sometimes more attention(not the nice style).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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