Investigate Release Builds with Debug Symbols under GDB for potential issues with rclrs_tests usage of DDS

[maspe36]

Investigate Release Builds with Debug Symbols under GDB for potential issues with rclrs_tests usage of DDS

[mxgrey]

I actually wasn't able to get gdb to work correctly on any test cases because the rapid creation and destruction of threads was leaving gdb without a stack to latch onto.

But it's reassuring that you're no longer reproducing it, and it's a good indication that this was a drop order issue on our end all along.

I'm skeptical that we're totally out of the woods yet. There may be potential drop orders that just don't happen to show up in our tests. So I'll still plan on auditing the rcl handlers more closely.

[maspe36]

@mxgrey I'm not sure how deep you dug here, but since #372 I haven't been able to reproduce this locally.

Going to close this for now.