-
Notifications
You must be signed in to change notification settings - Fork 947
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
Unable to attach with GDB when hitting GGML_ASSERT after backend v2 changes #630
Comments
Does this cause any issues? It's just meant to show a backtrace as a debugging aid, it is ok if in some cases it cannot be shown. |
The |
The only issue was that the debugger didn't stop and let me inspect the program state due to the missing abort() call. As you mention that exit is replaced with abort in llama.cpp -> I am closing this. |
Will likely sync after #625 is merged |
I use VS Code to debug a program through the Remote - SSH plugin with GDB. After this change:
![image](https://private-user-images.githubusercontent.com/8558655/287751137-23d15df4-bf19-4590-b026-595c00bd0cc7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAxODcwMTIsIm5iZiI6MTcyMDE4NjcxMiwicGF0aCI6Ii84NTU4NjU1LzI4Nzc1MTEzNy0yM2QxNWRmNC1iZjE5LTQ1OTAtYjAyNi01OTVjMDBiZDBjYzcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcwNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MDVUMTMzODMyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MzE1MjA5MDZkNzZlM2U1NDc4MGYxMmIwZmIyYTg1MGFjZTgyYWI3NzE1NTIzMmFiMWIzZDhhYjhjMDdhYmIyMCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.x8YP97oVCL_8RYJWM6hn_6JdXZxbUwEuqhpTqy5mQkg)
made in this PR #586 I am getting the bellow message, when I hit a ggml assert and gdb is unable to attach to the process.
If I replace ggml_print_backtrace(); with abort() it works as before (attaching with gdb as expected)
The text was updated successfully, but these errors were encountered: