--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: busybox: Segmentation fault in microcom applet
- From: Uwe Kleine-König <ukleinek@debian.org>
- Date: Wed, 25 Apr 2018 17:16:49 +0200
- Message-id: <152466940909.24672.9902119786947480276.reportbug@taurus.defre.kleine-koenig.org>
Package: busybox
Version: 1:1.27.2-2
Severity: normal
Hello
user@host:~$ busybox microcom
Segmentation fault (core dumped)
reproduces on two different amd64 machines. Could also reproduce on an
armel porter machine (abel, in the sid schroot).
1:1.22.0-19+b3 isn't affected.
Best regards
Uwe
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (700, 'testing'), (600, 'unstable'), (500, 'unstable-debug'), (500, 'stable'), (499, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages busybox depends on:
ii libc6 2.27-3
busybox recommends no packages.
busybox suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 896902-done@bugs.debian.org
- Subject: Re: Bug#896902: busybox: Segmentation fault in microcom applet
- From: Michael Tokarev <mjt@tls.msk.ru>
- Date: Mon, 9 May 2022 00:34:02 +0300
- Message-id: <d2ad6fd1-4f33-47b5-5410-4d227fd77dc2@msgid.tls.msk.ru>
- In-reply-to: <152466940909.24672.9902119786947480276.reportbug@taurus.defre.kleine-koenig.org>
- References: <152466940909.24672.9902119786947480276.reportbug@taurus.defre.kleine-koenig.org> <152466940909.24672.9902119786947480276.reportbug@taurus.defre.kleine-koenig.org>
Version: 1:1.30.1-1
On Wed, 25 Apr 2018 17:16:49 +0200 Uwe Kleine-König <ukleinek@debian.org> wrote:
Package: busybox Version: 1:1.27.2-2 Severity: normal
Hello
user@host:~$ busybox microcom Segmentation fault (core dumped)
reproduces on two different amd64 machines. Could also reproduce on an armel porter machine (abel, in the sid schroot).
1:1.22.0-19+b3 isn't affected.
This appears to be fixed since 1.28 upstream release and since 1.30.1-1 debian release.
Closing this bugreport now.
Thanks,
/mjt
--- End Message ---