Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Access violation for UHD_LOG_* #603

Open
SteamedBunInvasion opened this issue Jun 12, 2022 · 0 comments
Open

Access violation for UHD_LOG_* #603

SteamedBunInvasion opened this issue Jun 12, 2022 · 0 comments

Comments

@SteamedBunInvasion
Copy link

SteamedBunInvasion commented Jun 12, 2022

Issue Description

Using the UHD_LOG_INFO/UHD_LOG_ERROR/UHD_LOG_WARNING/UHD_LOG_TRACE/UHD_LOG_DEBUG will crash the application

Setup Details

windows 64 bit professional
USRP N210/B205mini
Visual Studio 2019
precompiled UHD win64 bit (https://files.ettus.com/binaries/uhd/latest_release/4.1.0.5/Windows-10-x64/uhd_4.1.0.5-release_Winx64_VS2019.exe) - also tried with the latest 4.2.0.0
precompiled libboost 1.78.0 (https://sourceforge.net/projects/boost/files/boost-binaries/1.78.0/boost_1_78_0-msvc-14.2-64.exe)

Expected Behavior

Produce a log line to the console.

Actual Behaviour

Exception thrown at 0x00007FF9D1C9BCFA (uhd.dll) in test_uhd_log.exe: 0xC0000005: Access violation reading location 0x0000000000003B30.
or
Exception thrown at 0x00007FF8AB7CBCFA (uhd.dll) in test_uhd_log.exe: 0xC0000005: Access violation reading location 0x000000CC000056D8.
or
Exception thrown at 0x00007FF8A22BBCFA (uhd.dll) in test_uhd_log.exe: 0xC0000005: Access violation reading location 0x000000C200004C58.
etc, the address is changed when using different log functions

Steps to reproduce the problem

Use the specified software/hardware (actully, you can also reproduce the error without the device itself)
Use any of the examples as a template and add a line to use the log. e.g.:
UHD_LOG_INFO("asasa", "asasas");

Additional Information

When compiling the source by myself in debug mode the error is not produced. when comiling with release mode the error is reproduced.
Sometimes, error with std::alloc might occur instead of access violation

@SteamedBunInvasion SteamedBunInvasion changed the title std::bad_alloc for UHD_LOG_* Access violation for UHD_LOG_* Jun 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants