-
Notifications
You must be signed in to change notification settings - Fork 492
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
gpgpusim : Aborted (core dumped) When run gpgpusim_simulation. #73
Comments
I am also facing the same error. Any update ? |
Thanks for raising the issue - is it just backprop that is failing, or are
all workloads encountering this issue?
Which OS are you using?
…On Mon, Jul 16, 2018 at 1:49 AM Sakala Venkata Krishna Rohit < ***@***.***> wrote:
I am also facing the same error. Any update ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#73 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD9McRGiqa2u4s7C8eb0Ew20UZeWFvdEks5uHClmgaJpZM4UOctb>
.
--
Tim Rogers
Assistant Professor
Purdue University
https://engineering.purdue.edu/tgrogers
|
Hi, @tgrogers Thanks for your caring. I was using the ubuntu 16 in a docker container and did not try other workloads. Here is the OS version: |
This likely comes from the change in the string ABI around c++11 discussed here: https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html. Ubuntu 16.04's c++ standard lib uses the dual ABI but g++ 4.x doesn't know about it you see the crash above. If you attach a debugger you'll see that it occurs in the option_parser and so is completely workload independent. Luckily the fix is relatively simple. Build gpgpu-sim using g++ 5.x (I've used 5.4 successfully) when using Ubuntu 16.04. This can create a bit of annoyance when working with CUDA 4.0 as 5.4 is above the max version nvcc will allow but you can switch gcc/g++ versions when compiling applications back to 4.x. |
Can confirm that I also ran into this issue attempting to compile with gcc-4.8 on Ubuntu 16.04. Solution was to compile with the built in gcc-5.4.0. |
Should we add some #if macro to judge the GCC version in OptionParse.cc? That problem may make a lot of trouble the guys new to GPGPUSIM( as to me before) |
Hello guys,I have the same question and I cannot build GPGPUsim successfully with GCC 5.4.0. Is there anyone know how to fix this issue? Thanks! |
one good method to solve this problem is to using gdb to debug it and when segment fault happened, using bt to print stack trace. I guess you can see the segment fault happened when parsing the args, be cause the libc++ cannot handle the exception from ostream throwout. try to refer to cppreference to find more detail about it
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: 赵威 <notifications@github.com>
Sent: Tuesday, October 8, 2019 5:45:48 AM
To: gpgpu-sim/gpgpu-sim_distribution <gpgpu-sim_distribution@noreply.github.com>
Cc: shenjiangqiu <ivy22233qiu@live.com>; Comment <comment@noreply.github.com>
Subject: Re: [gpgpu-sim/gpgpu-sim_distribution] gpgpusim : Aborted (core dumped) When run gpgpusim_simulation. (#73)
Hello guys,I have the same question and I cannot build GPGPUsim successfully with GCC 5.4.0. Is there anyone know how to fix this issue? Thanks!
―
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#73?email_source=notifications&email_token=AEM4BF3IGRE25WYOCAIXJ5DQNRJEZA5CNFSM4FBZZNN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEATSVIY#issuecomment-539437731>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEM4BF2ZW5V2WTJOENAXQMLQNRJEZANCNFSM4FBZZNNQ>.
|
Here is how i have resolved this issue in: Added .str() in the following lines in file cuda_runtime_api.cc best! |
@jayresearch I wonder if you still encountered the P.S. my OS version Ubuntu 19.10, arch x86_64, cuda 4.2.9 |
I was trying to run the gpgpu-sim_simulation.
When I was trying to run the benmark ibackprop, the following error pops:
The command I use is following:
The following are my work environment:
My cuda version is cudnn 4.2.
Is the error due to my cuda version? Is there anyone know how to fix this issue?
The text was updated successfully, but these errors were encountered: