Code::Blocks Forums

User forums => General (but related to Code::Blocks) => Topic started by: 51423benam on December 14, 2018, 06:44:27 pm

Title: Why don't we include a python enabled gdb with pretty printers as default?
Post by: 51423benam on December 14, 2018, 06:44:27 pm

Hello guys,

when I debugged in C::B the first time, I was pretty disappointed, as I was used to the VS debugger. The VS debugger is pretty comfortable, no need to alter anything, it just works out of the box. In Codeblocks however, I couldn't view the contents of, for example, STL containers. Now that has changed, since I finally got pretty printers working (which aren't THAT awesome either, they don't really work with nested variables and shared_ptrs and so on).
I think, the first impression to newbies is pretty bad when debugging. So why don't we include a python-enabled gdb per default (maybe even mingw-64?) and ship with enabled pretty printing? I think that would make things way easier.

Title: Re: Why don't we include a python enabled gdb with pretty printers as default?
Post by: 51423benam on February 17, 2019, 05:45:04 pm

Bump

Title: Re: Why don't we include a python enabled gdb with pretty printers as default?
Post by: oBFusCATed on February 17, 2019, 05:55:52 pm

If the gdb in mingw64 is python enabled the next version would probably have this working out of the box.