[Bug rust/26202] New: Support calling methods on types

[Bug rust/26202] New: Support calling methods on types

[dxu at dxuuu dot xyz]

https://sourceware.org/bugzilla/show_bug.cgi?id=26202

            Bug ID: 26202
           Summary: Support calling methods on types
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: rust
          Assignee: unassigned at sourceware dot org
          Reporter: dxu at dxuuu dot xyz
  Target Milestone: ---

For example, calling `Vec::len()` fails:

Breakpoint 1, rust_debug::foo () at src/main.rs:2
2           let v = vec!(1,2,3);
(gdb) n
3           println!("{:?}", v);
(gdb) p v.len()
Could not find function named 'alloc::vec::Vec<i32>::len'

It works for vectors in C++:

Temporary breakpoint 1, main () at main.cpp:4
4       int main() {
(gdb) n
5         std::vector<int> v{1,2,3};
(gdb) n
6         for (int i : v) {
(gdb) p v.size()
$1 = 3

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/26202] Support calling methods on types

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=26202

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I didn't look at the DWARF here, but in many cases the issue
is that rustc doesn't emit any information about traits; so
if a method is defined via a trait, then gdb simply can't know that.

Also, for C++, sometimes there are "xmethods" supplied by
libstdc++, so that this works even when the method is entirely
optimized away.  There's a gdb bug open about this topic
for Rust.

-- 
You are receiving this mail because:
You are on the CC list for the bug.