Update Linux Build Instruction #3923
Conversation
For Linux/ARM, you need to update libunwind-arm in order to avoid segmentation faults in libunwind-arm, which is not included in major Linux distros, yet, while it is already being addressed in upstreams. This is realted with #3898 Issue Comment 201098037: https://github.com/dotnet/coreclr/issues/3898#issuecomment-201098037 Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
|
thanks! |
|
LGTM. Thanks! |
|
@myungjoo Are you sure you need the protection on write too? |
|
@manu-silicon Yes, with test runs of coreclr in ARM/Linux, I've witnessed a case where I've got a segmentation fault with access_mem/write. Please refer this as well (from line 75,static int I'd like to test with android-libunwind installed instead of the default libunwind in non-Android machines for CORECLR later. (if somebody has done that, please share the results :) ) |
|
Curious to see that upstream libunwind is not doing the protection. Maybe we should contact them so that they add the protection too. |
|
@myungjoo Is this documentation still valid, or can I remove it? |
|
@BruceForstall If you are using libunwind 1.3 or later, it is no more required. If you are building with libunwind < 1.3, this is still valid. Note that libunwind has release 1.3 stable 3 months ago. |
Update Linux Build Instruction Commit migrated from dotnet/coreclr@58209af
For Linux/ARM, you need to update libunwind-arm
in order to avoid segmentation faults in libunwind-arm,
which is not included in major Linux distros, yet,
while it is already being addressed in upstreams.
This is realted with #3898 Issue Comment 201098037:
https://github.com/dotnet/coreclr/issues/3898#issuecomment-201098037
Signed-off-by: MyungJoo Ham myungjoo.ham@samsung.com