crash crashed with SIGSEGV in read()

Bug #2043785 reported by Benjamin Drung
This bug report is a duplicate of:  Bug #2043772: crash is crashy. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
coreutils (Ubuntu)
New
Medium
Unassigned

Bug Description

some description

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: coreutils 9.1-1ubuntu2.23.10.1
Uname: Linux 6.5.0-27-generic x86_64
Architecture: amd64
Date: Tue Apr 16 14:11:58 2024
ExecutablePath: /tmp/tmpn7izqail/crash
PackageArchitecture: amd64
ShortGibberish: "]¶"
Signal: 11
SourcePackage: coreutils
Stacktrace:
 #0 0x0000555555555143 in f (x=42) at crash.c:3
         p = 0x0
 #1 0x0000555555555164 in main () at crash.c:6
 No locals.
StacktraceTop:
 f (x=42) at crash.c:3
 main () at crash.c:6
UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sbuild sudo
separator:

Revision history for this message
Benjamin Drung (bdrung) wrote : Dependencies.txt
Revision history for this message
Benjamin Drung (bdrung) wrote : LongGibberish.txt
Revision history for this message
Benjamin Drung (bdrung) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2043772, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Revision history for this message
Benjamin Drung (bdrung) wrote : good retrace!

Stacktrace:
 long
 trace
StacktraceTop:
 read () from /lib/libc.6.so
 foo (i=1) from /usr/lib/libfoo.so
ThreadStacktrace:
 thread
 even longer
 trace

Changed in coreutils (Ubuntu):
importance: Undecided → Medium
summary: - crash crashed with SIGSEGV in f()
+ crash crashed with SIGSEGV in read()
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.