-
Notifications
You must be signed in to change notification settings - Fork 11.4k
std::runtime_error exceptions not caught as std::string by Visual C++? #1589
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
absolutely. also if compilers actually catch
... i'd recommend sending a bugreport to the compiler developers. that shouldn't be caught. |
It turns out that the current official release on github for x64 shows the same behaviour - apparently the codes mixes std::runtime_error and std::string exceptions in different parts. I will create an MR that makes this consistent. |
I'm facing same issue in Ubuntu 22.04.2 LTS x86_64. ./main -m ./models/7B/ggml-model-q4_0.bin --color -f ./prompts/alpaca.txt -ins --temp 0.8 --top_k 40 -n 5000 --repeat_penalty 1.3 --top_p 0.0 |
@rajivmehtaflex different issue. Also you probably need to regenerate your your q4_0.bin , it's most likely using an old format (because the format changed recently), which causes that exact error you posted. |
I'm having the same issue main: build = 0 (unknown) I hope this thread will solve it |
@Nyandaro also different issue. This issue is probably not the right place to debug it,
what do you get? |
What I did was download this repository as a ZIP sorry i don't know what that command means |
@Nyandaro
but this is not the right place to debug it. Maybe the guys over at https://SuperUser.com are willing to help you :) |
Platform: Windows x64
Commit: 7e4ea5b
I noticed that
main.exe
fails for me when I run it without any parameters, and no model is found. The only output I got was:In the debugger, I found that this line had triggered an unhandled exception:
When I change the
catch
statement like thisthen I get a proper error message again, as in the past:
This appears to be related to the changes made in #1316 that explicitly changed the exception type to
std::exception
, even though they are caught asstd::string
. Is this a specific behavior that only works in some compilers, and does it make sense for me to submit an MR that catches exceptions asstd::exception
as above, which appears to be more common C++ practice?My compiler version details (from CMake):
The text was updated successfully, but these errors were encountered: