Derek Bruening

If you want to submit a PR with some reasonable workaround for this compiler issue (probably with a comment about it) please do so; otherwise not seeing anything to do...

> Program received signal SIGILL, Illegal instruction. As explained here https://dynamorio.org/page_debugging.html#autotoc_md139 that is expected; just continue past it.

Trying to remind myself: so vsyscall is: ``` * app4: [0xFFFFFFFF'FF600000, 0xFFFFFFFF'FF601000]: vsyscall ``` It does not show up in the procfs maps file on my kernel. Was it removed...

Look like my kernel is running with `vsyscall=none` (https://github.com/torvalds/linux/blob/abfbb29297c27e3f101f348dc9e467b0fe70f919/Documentation/admin-guide/kernel-parameters.txt#L5535-L5553). So for that case, we can solve this: if we don't see 0xffffffff'ff6 we can eliminate the 0x7fff'ff4-0x7ff'ff8 gap. But it...

> Perhaps this new gap could be placed where the heap is approximately assumed to be. The application heap, i.e., the "break", right after the executable? I think that would...

Apps built with VS2017 should run under DrM, yes. I suspect that nobody has tried JMC before. We are a very small team and it is not easy to test...

I replied on #2184: have not been able to reproduce, but if it's purely address layout we should be able to resolve it once we have the layout information.

`ASSERT fastpath_x86.c:1004: mi->memsz

As already requested (!!! https://github.com/DynamoRIO/drmemory/issues/2232#issuecomment-712485938) please fill out the bug template. Without more information this report is not actionable.

> I ran with all the below options and it crashes just the same way with the same error messages above. That is impossible: `dynamorio/bin32/drrun` is not Dr. Memory and...