Alternative fix to #6468

[indutny]

Checklist

• tests and code linting passes
• a test and/or benchmark is included
• documentation is changed or added
• the commit message follows commit guidelines

Affected core subsystem(s)

deps

Description of change

Note: this PR should not be landed until this patch will be upstreamed to the v8's trunk.

Here I propose, instead of turning off ASLR at either runtime or compile-time, export the ASLR slide in the profile data and parse it to resolve the symbols during --prof-process.

Fix: #6466

[indutny]

cc @bnoordhuis

[indutny]

CI: https://ci.nodejs.org/job/node-test-pull-request/2433/

[ofrobots]

@indutny I like this approach. Can you propose this upstream?

[indutny]

@ofrobots just did it: https://codereview.chromium.org/1934453003/

[bnoordhuis]

You should probably print the slide as a signed base 10 number because it can be < 0. For that matter, the code should really be updated to use intptr_t because that's what _dyld_get_image_vmaddr_slide() returns.

[indutny]

Any pros of using unsigned int and base 10 here? I like how things may work both ways here.

[indutny]

Also, may I ask you to raise this concern on CL page?

[bnoordhuis]

Left a comment. The approach in general looks fine to me.

[indutny]

CL has just landed. Guess we should revisit this when it will gets to us with a v8 upgrade.

[indutny]

Superseded by #6558