Skip to content
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

No stack trace in paddle, may be caused by external reasons #74

Open
Pioneer-Weirdo opened this issue Aug 3, 2024 · 1 comment
Open

Comments

@Pioneer-Weirdo
Copy link


C++ Traceback (most recent call last):

No stack trace in paddle, may be caused by external reasons.


Error Message Summary:

FatalError: Segmentation fault is detected by the operating system.
[TimeInfo: *** Aborted at 1722663940 (unix time) try "date -d @1722663940" if you are using GNU date ***]
[SignalInfo: *** SIGSEGV (@0x0) received by PID 5695 (TID 0x7f370f34f280) from PID 0 ***]

Segmentation fault

@myhloli
Copy link
Collaborator

myhloli commented Aug 3, 2024

try to update paddlepaddle to 3.0.0b1 may could solve this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants