Author Topic: Support for Debugging STL library in C++  (Read 4156 times)

piyushj

  • Community Member
  • Posts: 28
  • Hero Points: 0
Re: Support for Debugging STL library in C++
« Reply #15 on: April 08, 2016, 12:47:40 pm »
Finally got it working for vector, map, deque etc.
But doesn't work on stack and queue.


Debug logs --
https://www.dropbox.com/s/rtyy1nre4ufpblw/debug.log?dl=1
Please look into this issue.

@pointing to ming gdb worked ! but only partially.

Also, in same setup, free codeblocks works fine, unlike slickedit.

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2815
  • Hero Points: 426
Re: Support for Debugging STL library in C++
« Reply #16 on: April 08, 2016, 03:22:13 pm »
I will check your debug logs, thanks for sending them.

Unfortunately, this is a forever-catching-up sort of issue.  The GDB/Python pretty printing integration is a poorly designed mechanism with respect to the GDB/MI (machine interface).  No attempt is made for the output of pretty printers to conform to the MI protocol, or to honor simple settings such as limits on how many elements of an array to print before stopping.  Try to print an oversized or uninitialized array, and GDB will hang and eventually run out of memory.  So, every release, they change something and create something new for debugger implementors to chase down and work around.  It's not going to change, but I felt like I should explain why we can not always keep up with this particular ever-changing target.

piyushj

  • Community Member
  • Posts: 28
  • Hero Points: 0
Re: Support for Debugging STL library in C++
« Reply #17 on: April 15, 2016, 04:22:17 pm »
Thanks. It's all fixed in new version.
 ;D ;D ;D