Bug 49283 - systemd-journalctl craches on MATCH multiple params
Summary: systemd-journalctl craches on MATCH multiple params
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Lennart Poettering
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-29 14:50 UTC by Maksim Melnikau
Modified: 2012-07-22 14:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Maksim Melnikau 2012-04-29 14:50:19 UTC 
# systemd-journalctl -o cat _PID=11937 _UID=0
lines ?-?/? (END)zsh: segmentation fault (core dumped)  systemd-journalctl -o cat _PID=11937 _UID=0

# systemd-journalctl -n 1 -o verbose
Mon, 30 Apr 2012 00:47:14 +0300 [s=bacf660eec8340c99fcc4e5a5858c8a8;i=1715;b=083530b34e7547e48fcfe7be0726fa3f;m=c68eb775e;t=4bed847dfe478;x=fc754ac694cd041c;p=system.journal]
        COREDUMP_UNIT=kdm@tty7.service
        COREDUMP_PID=20784
        COREDUMP_UID=0
        COREDUMP_GID=0
        COREDUMP_SIGNAL=11
        COREDUMP_COMM=systemd-journal
        COREDUMP_EXE=/usr/bin/systemd-journalctl
        COREDUMP_CMDLINE=systemd-journalctl -o cat _PID=11937 _UID=0
        COREDUMP_TIMESTAMP=1335736034000000
        MESSAGE_ID=fc2e22bc6ee647b6b90729ab34a250b1
        PRIORITY=2
        MESSAGE=Process 20784 (systemd-journal) dumped core.
        COREDUMP=[1.0M blob data]
        _TRANSPORT=journal
        _PID=20786
        _UID=0
        _GID=0
        _SOURCE_REALTIME_TIMESTAMP=1335736034909640
        _BOOT_ID=083530b34e7547e48fcfe7be0726fa3f
        _MACHINE_ID=be1598bd68baa268cb48e33d0000000f
        _HOSTNAME=m_melnikau-vaio
Comment 1 Lennart Poettering 2012-07-20 12:29:37 UTC 
Should be fixed in 187, please test!
Comment 2 Maksim Melnikau 2012-07-22 14:10:56 UTC 
Multiple match params work now, thanks!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.