Caliper Segmentation fault on Xeon Phi Knight landing
- Dominant language
- C
- Stars
- 88
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
I annotate LULESH with caliper macros. LULESH experienced segmentation fault with the following call stack information (More details, please refer to this [caliper issue](https://github.com/LLNL/Caliper/issues/30)) :
#0 0x00002b06b0cc005f in ?? ()
#1 0x00002b06b11c8041 in (anonymous namespace)::cali_pthread_create_wrapper (thread=0x7ffff8a1d0d8, attr=0x7ffff8a1d338,
fn=0x2b06b0d74eb0 <_INTERNAL_26_______src_z_Linux_util_cpp_313effc4::__kmp_launch_worker(void*)>, arg=0x2b06b490e400)
at /work/03915/taoncsu/stampede2/Caliper/src/services/pthread/PthreadService.cpp:83
#2 0x00002b06b0d759c9 in __kmp_create_worker (gtid=-123612968, th=0x7ffff8a1d338, stack_size=47307741232816) at ../../src/z_Linux_util.cpp:878
#3 0x00002b06b0d42579 in __kmp_allocate_thread (root=0x7ffff8a1d0d8, team=0x7ffff8a1d338, new_tid=-1323532624)
at ../../src/kmp_runtime.cpp:4521
#4 0x00002b06b0d472a7 in __kmp_allocate_team (root=0x7ffff8a1d0d8, new_nproc=-123612360, max_nproc=-1323532624, new_proc_bind=30692880,
new_icvs=0x0, argc=16, master=0x2b06b490f200) at ../../src/kmp_runtime.cpp:5138
#5 0x00002b06b0d45a18 in __kmp_fork_call (loc=0x7ffff8a1d0d8, gtid=-123612360, call_context=(unknown: 2971434672), argc=30692880,
microtask=0x0, invoker=0x10, ap=0x7ffff8a1d7b0) at ../../src/kmp_runtime.cpp:2150
#6 0x00002b06b0d1be2a in __kmpc_fork_call (loc=0x7ffff8a1d0d8, argc=-123612360,
microtask=0x2b06b11c7eb0 <(anonymous namespace)::thread_wrapper(void*)>) at ../../src/kmp_csupport.cpp:328
#7 0x000000000040434d in main ()
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked Caliper issue and reproduce the annotated LULESH run on Xeon Phi Knight Landing using the provided stack trace, especially cali_pthread_create_wrapper in src/services/pthread/PthreadService.cpp. Done means determining the cause of the segmentation fault and demonstrating that the annotated run no longer crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100