Enhancement #2065
Unintuitive exception in rsc::os::getProgramName in case of invalid PID for LinuxProcessInfo
Status: | Resolved | Start date: | 10/22/2014 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | J. Wienke | % Done: | 100% | |
Category: | Operating System Abstraction | |||
Target version: | Robotics Service Bus - rsb-0.11 |
Description
See #2058 for the original issue.
terminate called after throwing an instance of 'std::runtime_error' what(): Could not determine program name: basic_ios::clear
Related issues
Associated revisions
Better exception message for getProgramName
In case a process does not exist, throw something more intuitive than an
internal detail of the stream.
fixes #2065
History
#1 Updated by J. Wienke over 9 years ago
- Copied from Bug #2058: Starting the process-monitor with an incorrect PID leads to a strange error message added
#2 Updated by J. Wienke over 9 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset rsc|634e92ddd16cffadec09a10579dc7283247def2f.