-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caliper Segmentation fault on Xeon Phi Knight landing #40
Comments
Hey @twang15 , much appreciated. Any chance you could rerun it with GOTCHA_DEBUG set to 3? In the current state, I can't do much to test this (no KNL access). No stress if you can't, I have a request for KNL access in and will get you ready to go ASAP, but if you want quicker results it would be neat to be able to see the debug info. Best, David |
Hey David,
I have set that environment variable. But I did not see any debug
information. Please let me know where I should look for it? Is it dumped to
a file or on the screen?
I am actually at B315 now. If you want to debug it here, I can grant you
access to KNL.
…On Mon, Jul 3, 2017 at 12:53 David Poliakoff ***@***.***> wrote:
Hey @twang15 <https://github.com/twang15> , much appreciated. Any chance
you could rerun it with GOTCHA_DEBUG set to 3? In the current state, I
can't do much to test this (no KNL access). No stress if you can't, I have
a request for KNL access in and will get you ready to go ASAP, but if you
want quicker results it would be neat to be able to see the debug info.
Best,
David
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#40 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APd91oFB-SPweGkxghKGmxdwYzsyO0Loks5sKUaogaJpZM4OMm3p>
.
|
Sure, have an office number? I'll be right over |
Sorry for the delay. But, here it is c455-032.stampede2(17)$ GOTCHA_DEBUG=3 CALI_SERVICES_ENABLE=pthread ./a.out 5 |
@daboehme Is this still a issue? |
No idea, might have been fixed with the recent updates. Since it's 6 years old I believe we can mark it as closed. |
I annotate LULESH with caliper macros. LULESH experienced segmentation fault with the following call stack information (More details, please refer to this caliper issue) :
#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 ()
The text was updated successfully, but these errors were encountered: