-
Notifications
You must be signed in to change notification settings - Fork 13
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
"Segmentation fault" while running the code #6
Comments
Thanks @PavaniTatikonda22 -- we will look into this very soon. |
@wangyiqiu Did you get a chance to look into this issue? We would appreciate it if you could resolve this. Thanks! |
Hi @PavaniTatikonda22 I just tried the same commands you screenshotted above but I did not encounter any problem. I also tested it with Valgrind without discovering any problem. Could you send me a copy of your compiled binary to [email protected]? Thanks and sorry about the inconvenience. |
I also have this issue not in c++ but only in python bind here is the screenshot: Don't have any clue where the segment happened..... Looking forward to your reply. Thanks in advance. @wangyiqiu System info: |
When we tried to run the code on the CPU, It is throwing a "Segmentation fault (core dumped)", We ran the code on the below machine details:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 48
On-line CPU(s) list: 0-47
Thread(s) per core: 1
Core(s) per socket: 24
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 85
Model name: Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz
Stepping: 7
CPU MHz: 2100.000
BogoMIPS: 4200.00
L1d cache: 32K
L1i cache: 32K
L2 cache: 1024K
L3 cache: 36608K
NUMA node0 CPU(s): 0-23
NUMA node1 CPU(s): 24-47
It is the latest error that we are getting, we ran the same code 2 weeks back, and we didn't see any errors and ran the code successfully. Please let us know if any extra details are required.
The text was updated successfully, but these errors were encountered: