Bug #2058
Starting the process-monitor with an incorrect PID leads to a strange error message
| Status: | Rejected | Start date: | 10/13/2014 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | J. Wienke | % Done: | 0% | |
| Category: | - | |||
| Target version: | Robotics Service Bus - rsb-0.11 |
Description
What did I do?¶
/vol/toolkit/nightly/x86_64/last/bin/rsb-process-monitor0.11 --pid 168 -o /foo
Note that there is no process with id 168.
What happened?¶
terminate called after throwing an instance of 'std::runtime_error' what(): Could not determine program name: basic_ios::clear
Note the final word of the error message :)
What did I expect to happen?¶
The error should probably contain the process id.
Notes¶
This could be an upstream bug in Robotics Systems Commons.
Related issues
Associated revisions
Improve error messages in case a PID does not exist
Improved the error handling at process start in case a PID does not
exist. Now, a reasonable error message is given and everything is
stopped consistently without using the default exception handler.
refs #2058
History
#1 Updated by J. Wienke over 9 years ago
- Status changed from New to In Progress
- Target version set to rsb-0.11
#2 Updated by J. Wienke over 9 years ago
- Copied to Enhancement #2065: Unintuitive exception in rsc::os::getProgramName in case of invalid PID for LinuxProcessInfo added
#3 Updated by J. Wienke over 9 years ago
- Status changed from In Progress to Rejected
Yes, this is an upstream issue. See the related issue.