You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
breaking in main and stepping into f yields odd behaviour in gdb. Specifically, the first step into f shows pub fn main() {, the second shows f();, and the third takes us to the proper io::println("foo");. Disassembling at each step shows the first step takes us inside f into its prelude, so obviously we're not updating the source position correctly when generating the function.
The text was updated successfully, but these errors were encountered:
… r=jdm
This PR contains some code cleanup and the fix for issue #8670.
~~I am not sure about issue #8442 (could not reproduce it). @jdm, could check after this is merged and possibly close the issue then?~~ (closed now)
Some interesting facts: With this commit, it should be possible to compile libstd with `-Zdebug-info` (it does not work yet with `-Zextra-debug-info` but we are getting there). Switching debug info on increases the compile time for libstd by about 2 seconds.
@catamorphism I get one failing test in rustpkg:
`package_script_with_default_build` says: `task <unnamed> failed at 'Couldn't copy file', /home/mw/rust/src/librustpkg/tests.rs:689`
Would you have any idea what that is about? Seems be something wrong on my machine...
Cheers,
Michael
Fixes#8670
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Feb 24, 2022
With a simple setup like
breaking in main and stepping into f yields odd behaviour in gdb. Specifically, the first step into f shows
pub fn main() {
, the second showsf();
, and the third takes us to the properio::println("foo");
. Disassembling at each step shows the first step takes us insidef
into its prelude, so obviously we're not updating the source position correctly when generating the function.The text was updated successfully, but these errors were encountered: