tags 765070 + patch
thanks
I've found the reason for this!
In kfreebsd 9.2 or 10.x, kern.elf64.nxstack=1 by default, which means
executable stacks are not allowed. The segfault happens at:
| 1270: twalk(btree, idid_btree_builddescarray);
where function idid_btree_builddescarray() is defined on
found 765070 openrc/0.13.1-1
thanks
Hi,
Bug is still present in this version. I've attached a new backtrace
from running `rc-update -u`.
The bug is reproducible on kfreebsd-amd64 kernel versions 9.2 and 10.1
(jessie/sid), but not on 9.0 (wheezy). I can't think why that might be.
libkvm can be
FWIW libkvm is not being used any more. The attached debdiff removes
the unnecessary link and build-dependency.
I'll reply back in a few hours after testing openrc 0.13.1-1 it on
kfreebsd 10.1. I'm hopeful the crash bug was already fixed when the
libkvm-dependent code went away.
Regards,
--
St
Ritesh Raj Sarraf wrote:
> Thanks. Then can you please assign it to the appropriate package. This one
> right now is RC for openrc, marking it's removal from testing in a couple
> of days.
It's not clear yet that this bug is anywhere other than in openrc. It
does does crash (grave bug) on an up-t
Thanks. Then can you please assign it to the appropriate package. This one
right now is RC for openrc, marking it's removal from testing in a couple
of days.
s3nt fr0m a $martph0ne, excuse typ0s
On Oct 18, 2014 9:14 PM, "Steven Chamberlain" wrote:
> On 20:43, Ritesh Raj Sarraf wrote:
> > Thanks
On 20:43, Ritesh Raj Sarraf wrote:
> Thanks Steven. In that case, can we downgrade the severity of this bug ?
Not really; that is the kernel in sid/jessie, the one we plan to
release with.
But there's a possibility something is wrong in libkvm or kfreebsd and
we can reassign the bug in thet case
On Saturday 18 October 2014 08:09 PM, Steven Chamberlain wrote:
> On 19:31, Ritesh Raj Sarraf wrote:
>> > I believe Steven reproduced it with kFreeBSD 9.0.
> No sorry, I should have mentioned in my bug report, I was using
> kfreebsd 10.1 from jessie/sid. I didn't imagine this was kernel-
> specifi
On 10/18/2014 06:01 PM, Ritesh Raj Sarraf wrote:
> Dmitry:
>
> I believe Steven reproduced it with kFreeBSD 9.0.
Sorry for my total idiocy, but what should I do to repeat the bug?
Debian/kFreeBSD 7.6.0 [1] uses FreeBSD kernel of version 9.0 already:
# uname -a
GNU/kFreeBSD debian 9.0-2-amd64 #0
On 19:31, Ritesh Raj Sarraf wrote:
> I believe Steven reproduced it with kFreeBSD 9.0.
No sorry, I should have mentioned in my bug report, I was using
kfreebsd 10.1 from jessie/sid. I didn't imagine this was kernel-
specific.
But the affected code uses libkvm, so it could mean a kernel ABI break
Dmitry:
I believe Steven reproduced it with kFreeBSD 9.0.
Forwarded Message
Subject:Re: [PKG-OpenRC-Debian] Bug#765070: openrc: [kfreebsd]
segfault in loopsolver
Date: Sat, 18 Oct 2014 15:56:37 +0400
From: Dmitry Yu Okunev
Reply-To: OpenRC Debian Maintainers
The bug is triggerable on kfreebsd-amd64 with just `update-rc -u`.
Rebuilding without debian/patches/0020-dependency-loop-resolver.patch,
fixes the crash for me (in librc1).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Package: openrc
Version: 0.12.4+20131230-9
Severity: grave
Hi,
Installing openrc segfaults in postinst and subsequently at boot.
(Though it gave me a login shell, so I was at least able to bring
up the system manually and recover it).
I rebuilt without optimisations to get the attached backtrace
12 matches
Mail list logo
