-
Notifications
You must be signed in to change notification settings - Fork 226
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
[BUG] problems with long region names (segfaults and errors) #551
Comments
Hello from Cologne ;) problem is not urgent for me - as a workaround I just shorten my region names Best, |
Hi Melven, we have that issue also with others trying to integrate the MarkerAPI into some framework with auto-generated region names (e.g. OpenSYCL). The question is what is a reasonable maximal length for the region names. Or no string length limit at all? Your opinion? The currently hardcoded limit is 100 characters. Best, |
Hi Thomas, I suspect there is an additional bug: it should not segfault when the string is too long. Best, |
Please check the linked commit/branch. It follows your suggestion to truncate the region tag if larger than 100 characters. |
Works fine in all my tests, thanks! |
Describe the bug
With region names longer than ~100 characters, I get
not a valid region description: ...
sometimes followed by a segfault.To Reproduce
gcc -I/path/to/likwid/include -L/path/to/likwid/lib -llikwid -DLIKWID_PERFMON -fopenmp example.c
likwid-perfctr -g MEM_DP -C 0 -m ./a.out
Please supply the output of the command with
-d
added to the command line:Example code
The text was updated successfully, but these errors were encountered: