nano crashed with SIGSEGV in get_sysdep_segment_value()

Bug #1710511 reported by Wellington Torrejais da Silva
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nano (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

When update

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nano 2.8.6-2
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Aug 9 20:22:31 2017
ExecutablePath: /bin/nano
InstallationDate: Installed on 2017-08-09 (4 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170806)
ProcCmdline: nano /etc/defaults/grub
SegvAnalysis:
 Segfault happened at: 0x7fdda72da0f5 <_nl_find_msg+725>: mov (%r12),%rdi
 PC (0x7fdda72da0f5) ok
 source "(%r12)" (0x30b000003019) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nano
StacktraceTop:
 get_sysdep_segment_value (name=0x7fdda7cd3364 <error: Não é possível acessar a memória no endereço 0x7fdda7cd3364>) at loadmsgcat.c:727
 _nl_load_domain (domain_file=0x55d7c83aafc0, domainbinding=domainbinding@entry=0x0) at loadmsgcat.c:1002
 _nl_find_domain (dirname=dirname@entry=0x7fdda743ca40 <_nl_default_dirname> "/usr/share/locale", locale=locale@entry=0x7ffcc307a400 "pt", domainname=domainname@entry=0x7ffcc307a420 "LC_MESSAGES/libc.mo", domainbinding=domainbinding@entry=0x0) at finddomain.c:173
 __dcigettext (domainname=0x7fdda7435a40 <_libc_intl_domainname> "libc", msgid1=0x7fdda7435dfd "No such file or directory", msgid2=msgid2@entry=0x0, plural=plural@entry=0, n=n@entry=0, category=category@entry=5) at dcigettext.c:722
 __GI___dcgettext (domainname=<optimized out>, msgid=<optimized out>, category=category@entry=5) at dcgettext.c:47
Title: nano crashed with SIGSEGV in get_sysdep_segment_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Wellington Torrejais da Silva (wellington1993) wrote :
information type: Private → Public Security
information type: Public Security → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 get_sysdep_segment_value (name=0x7fdda7cd3364 <error: Cannot access memory at address 0x7fdda7cd3364>) at loadmsgcat.c:727
 _nl_load_domain (domain_file=0x55d7c83aafc0, domainbinding=domainbinding@entry=0x0) at loadmsgcat.c:1002
 _nl_find_domain (dirname=dirname@entry=0x7fdda743ca40 <_nl_default_dirname> "/usr/share/locale", locale=locale@entry=0x7ffcc307a400 "pt", domainname=domainname@entry=0x7ffcc307a420 "LC_MESSAGES/libc.mo", domainbinding=domainbinding@entry=0x0) at finddomain.c:173
 __dcigettext (domainname=0x7fdda7435a40 <_libc_intl_domainname> "libc", msgid1=0x7fdda7435dfd "No such file or directory", msgid2=msgid2@entry=0x0, plural=plural@entry=0, n=n@entry=0, category=category@entry=5) at dcigettext.c:722
 __GI___dcgettext (domainname=<optimized out>, msgid=<optimized out>, category=category@entry=5) at dcgettext.c:47

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nano (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Benno Schulenberg (bennoschulenberg) wrote :

The crash was in libc (while looking up the translation of a string), not in nano itself. Could it be that you updated libc shortly before the crash?

As this crash happened in an alpha release, and if you cannot reproduce it any more in 17.10 proper, I think this bug can be closed.

Changed in nano (Ubuntu):
status: New → Incomplete
Changed in nano (Ubuntu):
status: Incomplete → 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.