-
Notifications
You must be signed in to change notification settings - Fork 13.3k
gdb crashes when printing a vector before it is defined #32954
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
Comments
The Rust vector printer collects all the children at once:
However this is not recommended practice for gdb pretty-printers. Instead they should return a lazy iterator. gdb will limit the displayed length according to either user settings (like |
Also, this is issue #29467, which apparently has a patch. |
I think this is no longer an issue. When I tried, I'd get
|
Closing as fixed. Verified that the vector is printed locally when going to the next line. |
When debugging something like the following with
rust-gdb
And doing something silly like the following
gdb
freezes and will eventually be killed (on another of my machines a Python Exception is raised). This didn't occur with primitives (integer
,slice
,&str
), but Python Exceptions were raised withOption
,String
, etc., butVec
was the only one that causedgdb
to crash. Probably not too important since checking the values of items before they are defined is not useful.The text was updated successfully, but these errors were encountered: