| Summary: | Matching issues in coredumpctl | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Elias Probst <mail> |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
Hi, I think you misunderstood the manpage. It says that if you want to filter according to a PID, you just have to add PID as an argument like: coredumpctl list 6654 Without the PID=, but I can see why there is a confusion here, maybe adding examples in the manpage could help to clarify ? About gdb, there is no problem for me currently (with master). Yeah, appears to be a misunderstanding, as Ronny pointed out. The man page has been updated now to include an example to avoid the confusion. I figure that settles this bug. CLosing. |
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.
It looks like there are some problems in coredumpctl with matching entries of the list provided by 'coredumpctl list'. My listing here: TIME PID UID GID SIG PRESENT EXE Wed 2014-09-03 12:54:03 CEST 6650 1000 500 6 * /usr/bin/kglobalaccel5 Wed 2014-09-03 12:54:06 CEST 6651 1000 500 6 * /usr/lib64/libexec/drkonqi Wed 2014-09-03 14:25:54 CEST 5928 1000 500 6 * /usr/bin/kglobalaccel5 Wed 2014-09-03 14:25:57 CEST 5929 1000 500 6 * /usr/lib64/libexec/drkonqi Wed 2014-09-03 14:26:02 CEST 3303 1000 500 11 * /usr/bin/kded5 Wed 2014-09-03 14:26:03 CEST 5930 1000 500 11 * /usr/bin/kded5 Wed 2014-09-03 14:26:21 CEST 6007 1000 500 6 * /usr/bin/kglobalaccel5 Wed 2014-09-03 14:26:25 CEST 6050 1000 500 11 * /usr/bin/bluedevil-monolithic Wed 2014-09-03 14:33:40 CEST 6567 1000 500 6 * /usr/bin/kglobalaccel5 Wed 2014-09-03 14:33:42 CEST 6568 1000 500 6 * /usr/lib64/libexec/drkonqi Wed 2014-09-03 14:33:46 CEST 6569 1000 500 11 * /usr/bin/kded5 Wed 2014-09-03 14:33:46 CEST 5986 1000 500 11 * /usr/bin/kded5 Wed 2014-09-03 14:34:32 CEST 6654 1000 500 6 * /usr/bin/kglobalaccel5 Now I'd like to handle the last entry of the list (PID 6654). coredumpctl(5) says I should be able to use PID=6654 as match: % coredumpctl info PID=6654 No coredumps found. While COREDUMP_PID (suggested on IRC by dreisner) works: % coredumpctl info COREDUMP_PID=6654 PID: 6654 (kglobalaccel5) UID: 1000 (elias) GID: 500 (elias) Signal: 6 (ABRT) Timestamp: Wed 2014-09-03 14:34:31 CEST (27min ago) Command Line: /usr/bin/kglobalaccel5 Executable: /usr/bin/kglobalaccel5 Control Group: /user.slice/user-1000.slice/user@1000.service/dbus.service Unit: user@1000.service Slice: user-1000.slice Owner UID: 1000 (elias) Boot ID: ff9eec4b3e024935b724067f6b4305c4 Machine ID: c7a150de6cd901b63a1317770000000b Hostname: moria Coredump: /var/lib/systemd/coredump/core.kglobalaccel5.1000.ff9eec4b3e024935b724067f6b4305c4.6654.1409747671000000.xz Message: Process 6654 (kglobalaccel5) of user 1000 dumped core. Then again, using exactly this matching criteria for 'coredumpctl gdb' doesn't work: % coredumpctl gdb COREDUMP_PID=6654 No match found. So it looks like there are at least 2 issues: - the manpage is not consistent with the implementation - the implementation uses tool-specific (info, gdb, …) matching implementations Running current git master of systemd.