rticommunity / rticommunity/rticonnextdds-examples
Exception on Topic<> creation in Debug mode on Windows (x64)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 148
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Information
- RTI Product: RTI Connext
- Version: 6.0.1
- Operating system: Windows 10
- Compiler: VS2017
- Compiler version:
- Additional information:
What is the current behavior?
Unable to run a modern C++ example (c++03/11) when building a debug version on Windows x64.
'Release' versions run as expected.
'Debug' versions run fine on Linux.
Traditional c++ work fine.
The problem seems to be related to Windows/Debug builds.
An exception occurs when attempting to create the Topic<>
Tried several examples, they all exhibit similar problems.
E:\rticonnextdds-examples\examples\connext_dds\dynamic_data_using_publisher_subscriber\c++11
E:\rticonnextdds-examples\examples\connext_dds\asynchronous_publication\c++03
E:\rticonnextdds-examples\examples\connext_dds\partitions\c++03
Steps to reproduce the issuecd E:\rticonnextdds-examples\examples\connext_dds\dynamic_data_using_publisher_subscriber\c++11
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Debug -DBUILD_SHARED_LIBS=ON .. -G "Visual Studio 15 2017" -A x64
VS2017: rtiexamples-dynamic-data-using-publisher-subscriber.sln
Exception occurs on:
Topic topic(participant, "Square", shape_type);
Backtrace:
#1 RTIOsapiThread_newWithStack [0x40DF9930]
#2 UnhandledExceptionFilter [0xA409F400]
#3 memset [0xA6F22F80]
#4 _C_specific_handler [0xA6F0C5C0]
etc.
What is the expected behavior?
Suggested solutions
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure from the dynamic_data_using_publisher_subscriber/c++11 example using the supplied CMake Debug x64 command, then inspect the Topic construction. Compare the Windows Debug behavior with Release and Linux, and check the other listed c++03 examples for the same exception. Done means the affected Debug examples run past topic creation without the reported exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100