bloaty: VM range (0, 4) for label state_fd.6026 extends beyond base map about bloaty HOT 8 CLOSED

It also seems to happen for thread local variables:

$ cat test.c
static _Thread_local int a;

int
main()
{

        return (*(volatile int *)&a);
}
$ bloaty -d symbols ./a.out
bloaty: VM range (0, 4) for label a extends beyond base map

The cast to volatile int * is just there so that a doesn't get optimized away.

from bloaty.

I tried copying the debug symbols to the side and then stripping the binary then passing the debug symbol file back in with --debug-file but I still get the same error.

from bloaty.

I've got the same issue and bisected it to commit 1e49be4. Can you confirm that commit 2b1d89c works fine?

from bloaty.

Sorry for the breakage. I will add some debugging output that will make it easier to pinpoint the source of the bug.

This was introduced in some changes where Bloaty's coverage was greatly increased, but the new logic is also stricter than the old logic.

from bloaty.

get same error with -d option， also look for solution

from bloaty.

I am experiencing similar error.

from bloaty.

Can any of you send a binary that causes this error? The smaller the better.

from bloaty.

Ran on binaries installed on my system, here's one of the smaller ones:

• /nix/store/28mwpyfh46m5l8wc3ia5p5cnnf90fvcx-iproute2-4.15.0/bin/lnstat: http://ix.io/14Eh

With bloaty -d symbols I'm seeing:

bloaty: VM range (6311448, 18446744073709551615) for label main extends beyond base map

LMK if you can't reproduce or need more details.

from bloaty.