Go platform example segfault only on Ubuntu
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 46
- Forks
- 19
- Avg merge
- 13h 38m
- Merged PRs (30d)
- 19
Description
+ valgrind ./examples/GoPlatform/main
==3920== Memcheck, a memory error detector
==3920== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==3920== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==3920== Command: ./examples/GoPlatform/main
==3920==
==3920==
==3920== Process terminating with default action of signal 11 (SIGSEGV)
==3920== Bad permissions for mapped region at address 0x1A4001
==3920== at 0x1A4001: ??? (in /home/runner/work/examples/examples/examples/GoPlatform/main)
==3920== by 0x4A6E2E7: ???
==3920== by 0x1A3FCF: ??? (in /home/runner/work/examples/examples/examples/GoPlatform/main)
==3920==
==3920== HEAP SUMMARY:
==3920== in use at exit: 0 bytes in 0 blocks
==3920== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==3920==
==3920== All heap blocks were freed -- no leaks are possible
==3920==
==3920== For lists of detected and suppressed errors, rerun with: -s
==3920== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
./ci_scripts/all_tests.sh: line 75: 3920 Segmentation fault (core dumped) valgrind ./examples/GoPlatform/main
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with valgrind ./examples/GoPlatform/main on Ubuntu, then inspect the GoPlatform example and the surrounding test command in ci_scripts/all_tests.sh. Trace why the executable reaches the invalid mapped address, and verify that the example and full test script complete without a segmentation fault.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, ubuntu
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100