| Summary: | ABRT2: report_Logger configurator accepts arbitrary text in Append field | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Steve Tyler <stephent98> |
| Component: | abrt | Assignee: | Denys Vlasenko <dvlasenk> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | anton, dvlasenk, iprikryl, jmoskovc, kklic, mtoman, npajkovs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-11 09:40:37 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Steve Tyler
2011-04-06 21:38:14 UTC
abrt-action-print also accepts an arbitrary string for the "-a" (append) option:
$ /usr/bin/abrt-action-print -d ccpp-2011-03-29-13:47:38-2362/ -o x1.log -a foobar
The report was stored to x1.log
$ /usr/bin/abrt-action-print --help
Usage: abrt-action-print [-v] -d DIR [-o FILE] [-a yes/no]
Prints problem information to standard output or FILE
-v, --verbose Be verbose
-d DIR Dump directory
-o FILE Output file
-a yes/no Append to, or overwrite FILE
abrt-plugin-logger-2.0.0-4.fc15.x86_64
That's because the report_Logger event is missing the xml description which defines the option types. Without the xml is not possible to determine the option type, so ABRT just creates this simple window which is accepting an arbitrary text... We want to keep Logger as an example of a .xml-less reporter (one which only has a .conf file but not .xml file in /etc/abrt/events). I propose to not fix this. (In reply to comment #3) > We want to keep Logger as an example of a .xml-less reporter (one which only > has a .conf file but not .xml file in /etc/abrt/events). > > I propose to not fix this. An "example" reporter sounds like a good idea. But does it have to be identical to a "deployed" reporter? They could be derived from the same source, perhaps. abrt-devel appears to already have an example reporter ... $ rpm -ql abrt-devel /usr/include/abrt /usr/include/abrt/abrt_exception.h /usr/include/abrt/abrt_types.h /usr/include/abrt/abrt_xmlrpc.h /usr/include/abrt/abrtlib.h /usr/include/abrt/action.h /usr/include/abrt/analyzer.h /usr/include/abrt/comm_layer_inner.h /usr/include/abrt/crash_types.h /usr/include/abrt/database.h /usr/include/abrt/dbus_common.h /usr/include/abrt/debug_dump.h /usr/include/abrt/observer.h /usr/include/abrt/plugin.h /usr/include/abrt/reporter.h /usr/include/abrt/xfuncs.h /usr/lib64/libABRTUtils.so /usr/lib64/libABRTdUtils.so /usr/lib64/libbtparser.so /usr/lib64/pkgconfig/abrt.pc /usr/share/doc/abrt-devel-1.1.17 /usr/share/doc/abrt-devel-1.1.17/abrt-plugin /usr/share/doc/abrt-devel-1.1.17/abrt-plugin/abrt-plugin /usr/share/doc/abrt-devel-1.1.17/abrt-plugin/abrt-plugin/HelloWorld.conf /usr/share/doc/abrt-devel-1.1.17/abrt-plugin/abrt-plugin/Makefile /usr/share/doc/abrt-devel-1.1.17/abrt-plugin/abrt-plugin/abrt-reporter-hello-world.cpp /usr/share/doc/abrt-devel-1.1.17/abrt-plugin/abrt-plugin/abrt-reporter-hello-world.h /usr/share/doc/abrt-devel-1.1.17/howto-write-reporter (In reply to comment #4) > (In reply to comment #3) > > We want to keep Logger as an example of a .xml-less reporter (one which only > > has a .conf file but not .xml file in /etc/abrt/events). > > > > I propose to not fix this. > > An "example" reporter sounds like a good idea. > But does it have to be identical to a "deployed" reporter? > They could be derived from the same source, perhaps. If the reporter will not be installed, it will receive much less testing. Considering that Logger is not only an example (that it may be useful for real world cases), I am trying to kill two birds with one stone here: (1) have a reporter which saves to a file (2) have a .xml-less reporter, to make sure this feature hasn't bit rotted. Here the solution may be to make boolean params look nicer even in non-xml reporters. (In reply to comment #6) > (In reply to comment #4) > > (In reply to comment #3) > > > We want to keep Logger as an example of a .xml-less reporter (one which only > > > has a .conf file but not .xml file in /etc/abrt/events). > > > > > > I propose to not fix this. > > > > An "example" reporter sounds like a good idea. > > But does it have to be identical to a "deployed" reporter? > > They could be derived from the same source, perhaps. > > If the reporter will not be installed, it will receive much less testing. > > Considering that Logger is not only an example (that it may be useful for real > world cases), I am trying to kill two birds with one stone here: > (1) have a reporter which saves to a file > (2) have a .xml-less reporter, to make sure this feature hasn't bit rotted. > > Here the solution may be to make boolean params look nicer even in non-xml > reporters. How would you do that? All I can think of is: "Append?" "y*": yes "n*": no other: report error That's more of a CLI implementation than a GUI implementation, but it would fix this bug ... We have /etc/libreport/events/report_Logger.xml now, which has this: <option type="bool" name="Logger_Append"> Thus, GUI shows a checkbox, not a text field now. Tested. |