Line numbers in stack traces #1043
Labels
A-debuginfo
Area: Debugging information in compiled programs (DWARF, PDB, etc.)
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
Milestone
Comments
|
Related to #237 |
ghost
assigned 
|
This was working at one point, but it doesn't seem to be any more. I have suspicions that the shift to using a bunch of libraries broke it, but I'm investigating. |
|
I saw line numbers in my stack traces today. It was awesome. That's all. |
|
It's something to do with that LLVM patch I had you revert and the way directory prefixes are handled by LLVM and the debuginfo generator. There haven't been line numbers in any debug build of rustc that I have built. |
|
Pretty sure that this is fixed with my latest round of debuginfo changes from last month. |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Apr 9, 2015
As pointed out in [RFC issue 1043][rfc] it is quite useful to have the standard I/O types to provide the contract that they are the sole owner of the underlying object they represent. This guarantee enables writing safe interfaces like the `MemoryMap` API sketched out in that issue. [rfc]: rust-lang/rfcs#1043 As constructing objects from these raw handles may end up violating these ownership gurantees, the functions for construction are now marked unsafe. [breaking-change] Closes rust-lang#1043
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
* Add test for `sinf32` * Add test for `sinf64` * Add test for `cosf32` * Add test for `cosf64` * Minor fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We get function names currently but not line numbers.
The text was updated successfully, but these errors were encountered: