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

too many PC-guards #88

Open
matthiaskrgr opened this issue Jun 6, 2024 · 1 comment
Open

too many PC-guards #88

matthiaskrgr opened this issue Jun 6, 2024 · 1 comment

Comments

@matthiaskrgr
Copy link

I already tried to apply the workaround from #19

/* Size (in bytes) for report data to be stored in stack before written to file */
#define _HF_REPORT_SIZE 32768
// #https://github.com/google/honggfuzz/commit/e2be7a962bad2ab1598b8ae1f55103968096c82c
/* Perf bitmap size */
#define _HF_PERF_BITMAP_SIZE_16M   (1024U * 1024U * 16U)
#define _HF_PERF_BITMAP_BITSZ_MASK 0x7FFFFFFULL
/* Maximum number of PC guards (=trace-pc-guard) we support */
// FIXED
#define _HF_PC_GUARD_MAX (1024ULL * 1024ULL * 128ULL)
// FIXED
/* Maximum size of the input file in bytes (1 MiB) */
#define _HF_INPUT_MAX_SIZE (1024ULL * 1024ULL *128ULL)

But to no avail
[2024-06-06T03:18:01+0200][F][66490] instrumentReserveGuard():263 This process requested too many PC-guards, total:135709549, requested:3479732)

When I try #define _HF_PC_GUARD_MAX (1024ULL * 1024ULL * 256ULL * 16ULL)

I get linker errors

text+0x122): relocation R_X86_64_PC32 out of range: 4461809218 is not in [-2147483648, 2147483647]; references section '.bss'
          >>> referenced by performance.c:33 (libhfuzz/performance.c:33)

#define _HF_PC_GUARD_MAX ULLONG_MAX didn't work either. 😅 any ideas?

@matthiaskrgr
Copy link
Author

I yeeted the entire check from the hf-rs sources in my cargo cache which seems to be somewhat of a workaround but im not sure what the side effects of this are... 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant