GDB 7.0 released
GDB 7.0 released
Posted Oct 9, 2009 9:07 UTC (Fri) by nix (subscriber, #2304)In reply to: GDB 7.0 released by njs
Parent article: GDB 7.0 released
Posted Oct 15, 2009 8:26 UTC (Thu)
by elanthis (guest, #6227)
[Link] (2 responses)
GDB needs a big push in the debug info department. It could use a big push in the compile time error quality, too, for that matter.
Posted Oct 15, 2009 8:56 UTC (Thu)
by jwakely (subscriber, #60262)
[Link] (1 responses)
GCC has to "slap in" the full type name for the linker, typedefs do not affect the name the linker uses.
GDB needs a big push in the debug info department.
You mean GCC, right? It's getting a big push, see http://gcc.gnu.org/wiki/Var_Tracking_Assignments
It could use a big push in the compile time error quality, too, for that matter.
See http://gcc.gnu.org/wiki/Better_Diagnostics - although it's easy to say diagnostics should be better, it's a lot harder to suggest specific improvements.
Posted Oct 15, 2009 11:33 UTC (Thu)
by jwakely (subscriber, #60262)
[Link]
... and this isn't true. GDB can show a more useful representation of data structures than simply listing all the bases and members, and that's exactly what the new python pretty printing does.
GDB 7.0 released
A lot of that is GCC's fault, really. GDB can only present the information present in the debug info, so if GCC is just slapping in the fully expanded instantiated types, then that's all GDB can give the user.
GDB 7.0 released
GDB can only present the information present in the debug info, so if GCC is just slapping in the fully expanded instantiated types, then that's all GDB can give the user.
GDB 7.0 released