Skip to content

u8 doesn't map to known type in MSVC-build debug info #39776

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

Closed
AndrewGaspar opened this issue Feb 13, 2017 · 1 comment
Closed

u8 doesn't map to known type in MSVC-build debug info #39776

AndrewGaspar opened this issue Feb 13, 2017 · 1 comment

Comments

@AndrewGaspar
Copy link
Contributor

I've built a rust program with this source code, compiling with the stable-x86_64-pc-windows-msvc toolchain:

fn main() {
    let some_8_bit_values = [0u8,1,2,3];
    let some_16_bit_values = [0u16,1,2,3];
    let some_32_bit_values = [0u32,1,2,3];
    let some_64_bit_values = [0u64,1,2,3];

    println!("Hello, world!");
}

I debugged the program with windbg. After all four arrays are initialized, I ran dv:

0:000> dv
Type information missing error for some_8_bit_values
some_16_bit_values = unsigned short [4]
some_32_bit_values = unsigned int [4]
some_64_bit_values = unsigned int64 [4]

The u16, u32, and u64 values all map to well known C-types of the same width, and windbg is able to display useful information about them, as if they were typical C-arrays:

0:000> dx some_16_bit_values
some_16_bit_values                 [Type: unsigned short [4]]
    [0]              : 0x0 [Type: unsigned short]
    [1]              : 0x1 [Type: unsigned short]
    [2]              : 0x2 [Type: unsigned short]
    [3]              : 0x3 [Type: unsigned short]

However, it appears that windbg can't do anything useful with the u8 array:

0:000> dx some_8_bit_values
Type information missing error for some_8_bit_values
Error: Unable to bind name 'some_8_bit_values'

I'm trying to write some NatVis visualizations for Rust debugging in windbg/the VS debugger, and this is making it difficult to write visualizations for std::string::String, for example.

I'd be happy to submit a patch myself, I'm just not familiar enough with the code to know where to start.

@AndrewGaspar
Copy link
Contributor Author

Sorry, this seems to be a duplicate of #36646. Closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant