Re: more information in backtraces

2012-07-12 Thread David Faure
On Thursday 12 July 2012 19:37:16 Dominik Haumann wrote: > On Thursday, 12. July 2012 18:13:22 David Faure wrote: > > On Thursday 05 July 2012 15:39:33 Dominik Haumann wrote: > > > Here, startPos is a Cursor, but we cannot see its values. > > > > > > It would help tremendously sometimes to know th

Re: more information in backtraces

2012-07-12 Thread Dominik Haumann
On Thursday, 12. July 2012 18:13:22 David Faure wrote: > On Thursday 05 July 2012 15:39:33 Dominik Haumann wrote: > > Here, startPos is a Cursor, but we cannot see its values. > > > > It would help tremendously sometimes to know the line/column values. So > > having "startPos=(4, 2)" instead of "s

Re: more information in backtraces

2012-07-12 Thread David Faure
On Thursday 05 July 2012 15:39:33 Dominik Haumann wrote: > Here, startPos is a Cursor, but we cannot see its values. > > It would help tremendously sometimes to know the line/column values. So > having "startPos=(4, 2)" instead of "startPos=...". > > Is there any way to provide this feature to ge

Re: more information in backtraces

2012-07-05 Thread Andreas Pakulat
Hi, On Thu, Jul 5, 2012 at 4:14 PM, Dominik Haumann wrote: > On Thursday, July 05, 2012 03:56:16 PM Andreas Pakulat wrote: > > On Thu, Jul 5, 2012 at 3:39 PM, Dominik Haumann > wrote: > > > Is there any way to provide this feature to get better backtraces by > > > default in Dr. Konqi? > > > >

Re: more information in backtraces

2012-07-05 Thread Dominik Haumann
On Thursday, July 05, 2012 03:56:16 PM Andreas Pakulat wrote: > On Thu, Jul 5, 2012 at 3:39 PM, Dominik Haumann wrote: > > Is there any way to provide this feature to get better backtraces by > > default in Dr. Konqi? > > It might work with gdb's pretty-printers, but dr. konqi needs to load them

Re: more information in backtraces

2012-07-05 Thread Andreas Pakulat
Hi, On Thu, Jul 5, 2012 at 3:57 PM, Christoph Feck wrote: > On Thursday 05 July 2012 15:39:33 Dominik Haumann wrote: > > Hi, > > > > in Kate, we have a (virtual) Cursor class: > > > > class Cursor > > { > > // public functions > > > > private: > > int m_line; > > int m_column > > };

Re: more information in backtraces

2012-07-05 Thread Christoph Feck
On Thursday 05 July 2012 15:39:33 Dominik Haumann wrote: > Hi, > > in Kate, we have a (virtual) Cursor class: > > class Cursor > { > // public functions > > private: > int m_line; > int m_column > }; > > Unfortunately, in backtraces by Dr. Konqi we only get: > #11 0x7f1c85128b2a

Re: more information in backtraces

2012-07-05 Thread Andreas Pakulat
Hi, On Thu, Jul 5, 2012 at 3:39 PM, Dominik Haumann wrote: > Hi, > > in Kate, we have a (virtual) Cursor class: > > class Cursor > { > // public functions > > private: > int m_line; > int m_column > }; > > Unfortunately, in backtraces by Dr. Konqi we only get: > #11 0x7f1c85128b2

more information in backtraces

2012-07-05 Thread Dominik Haumann
Hi, in Kate, we have a (virtual) Cursor class: class Cursor { // public functions private: int m_line; int m_column }; Unfortunately, in backtraces by Dr. Konqi we only get: #11 0x7f1c85128b2a in KateLayoutCache::updateViewCache (this=0x54db630, startPos=..., newViewLineCount=3