Ubuntu
groff package

troff crashed with SIGSEGV

Bug #1942974 reported by Erich Eickmeyer on 2021-09-08

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Groff	Unknown	Unknown	savannah #59202
	groff (Ubuntu)	Fix Released	Medium	Colin Watson

Bug Description

Crash occurred while running lintian, was reproducible with every run.

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: groff-base 1.22.4-6
ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
Uname: Linux 5.13.0-14-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu68
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Sep 7 15:02:26 2021
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/troff
InstallationDate: Installed on 2021-03-20 (171 days ago)
InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320)
ProcCmdline: troff -mandoc -rLL=117n -rLT=117n -wmac -Tutf8
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: groff
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: troff crashed with SIGSEGV
UpgradeStatus: Upgraded to impish on 2021-06-13 (86 days ago)
UserGroups: adm audio cdrom dip libvirt lpadmin plugdev sambashare sudo
separator:

Tags:

Revision history for this message

Erich Eickmeyer (eeickmeyer) wrote on 2021-09-08:

#1

Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (64.5 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (4.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Registers.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2021-09-08:

#2

StacktraceTop:
?? ()
cleanup_and_exit (exit_code=exit_code@entry=1) at ../../src/roff/troff/div.cpp:562
do_error (type=type@entry=FATAL, format=format@entry=0x56098d3fe3a5 "error writing output file", arg1=..., arg2=..., arg3=...) at ../../src/roff/troff/input.cpp:8616
fatal (format=format@entry=0x56098d3fe3a5 "error writing output file", arg1=..., arg2=..., arg3=...) at ../../src/roff/troff/input.cpp:8660
real_output_file::~real_output_file (this=0x56098e967920, __in_chrg=<optimized out>) at ../../src/roff/troff/node.cpp:1662

tags:

removed: need-amd64-retrace

Revision history for this message

Apport retracing service (apport) wrote on 2021-09-09: Stacktrace.txt

#4

Stacktrace.txt Edit (4.2 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2021-09-09: StacktraceSource.txt

#5

StacktraceSource.txt Edit (8.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2021-09-09: ThreadStacktrace.txt

#6

ThreadStacktrace.txt Edit (4.3 KiB, text/plain)

Changed in groff (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Brian Murray (brian-murray) wrote on 2021-09-09:

#7

This errors bucket looks similar:

https://errors.ubuntu.com/problem/6d78649d7439b32bd30780579ee872490ed5e339

Revision history for this message

Colin Watson (cjwatson) wrote on 2021-09-09:

#8

The stack trace looks very much like it would be the effect of https://savannah.gnu.org/bugs/index.php?59202, fixed in https://git.savannah.gnu.org/cgit/groff.git/commit/?id=c788cf8c6bbe939fa11f7ec032e525a7e33f41b6.

Colin Watson (cjwatson) on 2021-09-10

Changed in groff (Ubuntu):
status:	New → Fix Committed
assignee:	nobody → Colin Watson (cjwatson)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2021-09-10:

#9

This bug was fixed in the package groff - 1.22.4-7

---------------
groff (1.22.4-7) unstable; urgency=medium

* Cherry-pick from upstream:
- Fix SEGV arising from recursing destructor (LP: #1942974).

-- Colin Watson <email address hidden> Thu, 09 Sep 2021 18:20:47 +0100

Changed in groff (Ubuntu):
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

savannah #59202 Edit

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