map_server: Initialise NodeHandle outside the MapServer constructor #1122
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently if an exception is raised inside the
MapServer
execution, it's caught by thetry-catch
statement inmain
. However at that point theros::NodeHandle
instance is already destroyed since it's constructed insideMapServer::MapServer
and that's initialised inside thetry
scope.Because of that the
ROS_ERROR
statement in thecatch
doesn't print anything and the user isn't informed of the exception.In this PR I'm initialising
the NodeHandle outsideMapServer
and I'm passing a reference to it during construction.a second NodeHandle outside
MapServer
inmain