21for more information.
22
23▶# Function debuginfo
24
25## Tips
· · ·
43(13:56:12) bjorn3: for more context: https://github.com/bjorn3/rustc_codegen_cranelift/pull/978
44(13:58:16) osa1 verliet de ruimte (quit: Quit: osa1).
45▶(13:58:28) bjorn3: luispm: wait, for b m<TAB> it shows nothing, but when stepping into a new function it does
46(13:58:45) bjorn3: it still doesn't show anything for `info args` though
47(13:58:50) bjorn3: No symbol table info available.
· · ·
48(14:00:50) luispm: bjorn3, Is that expected given the nature of the binary?
49▶(14:01:17) bjorn3: b main<TAB> may show nothing as I only set DW_AT_linkage_name and not DW_AT_name
50(14:01:24) bjorn3: info args should work though
51(14:03:26) luispm: Sorry, I'm not sure what's up. There may be a genuine bug there.
· · ·
85(15:46:18) tromey: (which is really pretty good, most compilers manage to generate a bunch)
86(15:46:29) tromey: and then the gdb DWARF reader says
87▶(15:46:34) tromey: /* Ignore functions with missing or empty names. These are actually
88(15:46:34) tromey: illegal according to the DWARF standard. */
89(15:46:34) tromey: if (name == NULL)
· · ·
101(15:49:02) tromey: sort of anyway
102(15:49:43) tromey: this seems kind of pedantic of gdb, like if there's a linkage name but no DW_AT_name, then why bail?
103▶(15:50:01) tromey: also what about anonymous functions
104(15:50:17) tromey: but anyway this explains the current situation and if you don't mind adding DW_AT_name, then that's probably simplest
105(15:51:47) bjorn3: i added DW_AT_name.
+ 2 more matches in this file