Re: Bug#1086795: rsyslog: Segmentation fault
Michael Biebl <[email protected]> Tue, 18 Nov 2025 23:22:17 +0100
| Newsgroups | gmane.linux.debian.ports.powerpc |
|---|---|
| Message-ID | <[email protected]> |
No upstream bug has been filed and I haven't received any input/help from debian-powerpc porters. As I'm not even sure if the issue is still valid on ppc, I'm going to close this issue as I don't think it makes sense to keep it open indefinitely. If ppc porters want to chime in here and help debug this issue, we can reopen the bug report. Michael On Fri, 8 Nov 2024 12:58:33 +0100 Michael Biebl <[email protected]> wrote: > Control: tags -1 + help > > Hi Stuart > > Am 08.11.24 um 00:29 schrieb Stuart MacIntosh: > > > >> On 7/11/2024, at 1:25 AM, Michael Biebl <[email protected]> wrote: > >> > >> Control: tags -1 + moreinfo > >> Control: retitle -1 rsyslog: segmentation fault on ppc64 > >> > >> Am 06.11.24 um 00:18 schrieb Stuart MacIntosh: > >>> Package: rsyslog > >>> Version: 8.2406.0-1 > >>> Severity: grave > >>> Justification: renders package unusable > >>> Dear Maintainer, > >>> The rsyslog package on ppc64 in sid currently segfaults on Apple Xserve > >>> G5 hardware. > >> > >> Please provide a backtrace of the crash: > >> https://wiki.debian.org/HowToGetABacktrace > >> > >> > >> I also usertagged the issue so it shows up at [1] so the ppc porters might have a look and can keep track of it. > >> > >> Michael > >> > >> > >> > >> [1] https://udd.debian.org/cgi-bin/[email protected]&tag=ppc64 > > > > Please find the backtrace bt.txt attached. > > > > Thank you for your help. > > Thanks for the backtrace > > This looks like a crash in glibc when trying to load the rsyslog modules > from /usr/lib/rsyslog which in turn hints at a platform specific > (toolchain) issue. > > Not sure, if there is anything in rsyslog itself that can be done about > it (probably not). That said, I'm not familiar with the > intricacies of the ppc platform, so this issue needs help from the ppc > porters. > I will not further pursue this issue (as I lack the means to reproduce > the issue) and I will also not forward this issue to upstream. > You are free to try that though. In this case please report this at > https://github.com/rsyslog/rsyslog/issues > > Regards > Michael
OpenPGP_signature.asc
(application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEECbOsLssWnJBDRcxUauHfDWCPItwFAmkc8ZkFAwAAAAAACgkQauHfDWCPItwC rw/+OavG1Wp4Qw8RQkJmO8XiaEfkj8mxKnMBvp/PLsDTY2EBOp63m25zGxYt/GSUxpSdINQvHOxX diTzW39rLU0MJcgWMrgc/hYvheNM9CrvhNZVZfykbpcNu4ti1oSUpXsvaEClf0sXtjBANmIxtMYt gSpzc+polpWW+Cq2f7fWk+2NrO9+QIvi0WxrshvTrrFz1wsYlytJXEhw5ZiRWv9vVvqrcuQcgvI6 iDPgjb/DOZoph75zp26H27At3znx3KFz++ox72KxmV4L9AZ/vyFjAd3i4IvogjlnKxkoZWbn4CM9 yGrSzZKmpLT/QN7OT5MK/CKP3T/9L7cwDwF9jWT/Nql7Hs7jh79WSlN+mDIEVL2WnHptkK8aMxi3 cWl4wfecEOK24mukZzlida/CQV0uVAiDPmKn4ewUORAp4nqfnA7IQmmRW8Uz7wM97EeoxuTgJBfW egSDC05IFPUK4B5/Z7PyaLUIZwyTVGLEUuoAv8sqAncYYGfAvjFQdf+Gt25k7JI/n68swx/jlBZg Sf8PxGHLrtTRsWi3W1SyHp6ZJgxJrBeZmLHtqmwSvVA+emG8xxpc+/z6C2M+zwaO2uwq12GPCDf3 VQ/2roQtIzEjKH5HDckZUGGRdjPjJjWjCMYMjvZwncKqTCqNqQXX6a9RmPQy5hr2j2MCSiFifZrN 4a8= =7F1R -----END PGP SIGNATURE-----