Am 03.05.2012 21:12, schrieb Sven Anders: > Am 03.05.2012 18:33, schrieb Lennart Poettering: >> On Thu, 03.05.12 18:14, Sven Anders ([email protected]) wrote: >> >>> I'm getting some SegFaults, which I can not explain. I think the problem >>> lies somewhere in my configuration or systemd makes some assumptions and >>> my system does not fulfill these requirements. >>> >>> Nevertheless, I think the tools should not SegFault but issue an error >>> instead. By now I have no real idea where the problem lies. >>> If I run the tool in valgrind, they work. >> >> Hmm, I don't see how a system call would result in a SIGSEGV. This is >> really weird... >> >> The fd[] array passed to pipe() is allocated on the stack. This suggests >> that your stack is getting corrupted somehow. >> >> Do things work correctly if you run stuff with --no-pager? > > Curiously not. Only if I run this in valgrind... > > I had another strange SegFault when using systemd-journalctl, but this > is now gone... So I suspected a misconfiguration first... > > This is the same compilation and other tools and systemd itself are > running fine. I'm trying this in KVM with Linux kernel 3.2.2.
This only sees to happen, if I link the binaries with -pie . Have no idea what is causing this yet. Will investigating this further... Regards Sven Anders -- Sven Anders <[email protected]> () UTF-8 Ribbon Campaign /\ Support plain text e-mail ANDURAS intranet security AG Messestrasse 3 - 94036 Passau - Germany Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55 Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
<<attachment: anders.vcf>>
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
