fixed font for variable values (Was: MI branch merge)

On Saturday 20 May 2006 13:14, Andras Mantia wrote:
> On Friday 19 May 2006 17:30, Vladimir Prus wrote:
> > Hi,
> > the MI branch, which was in development since
2006-01-30, and has 100
> > commits on it at the moment, was just merged to
KDevelop 3.4 branch,
> > in revision 542513.
>
> I didn't really tested, but a small comment regarding
the Variables
> view: in KDevelop 3.3 the variable values were
displayed in a non-fixed
> sized font and now the font used is fixed sized
(Courier 10 pitch?).
> The problem is that even on a large display (I have
1280x1024) it takes
> too much space and you see too little from the variable
value. I
> suggest to switch back to a font which is less wider.
If you want, I
> can send screenshots with the difference.

The thing is that when say, looking at pointer values, fixed
font is *much* 
better (IMO). And use smaller font size can make things
unreadable. I'm at 
loss.

> Oops, I got a crash when trying to unset a breakpoint
(the currently
> debugged line was I believe the line on which the
breakpoint was):
> Using host libthread_db library
"/lib64/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread 47913848629312 (LWP 4105)]
> [New Thread 1082132800 (LWP 4126)]
> [KCrash handler]
> #5  0x0000000000000191 in ?? ()
> #6  0x00002b93cf7f6121 in __dynamic_cast ()

That's not yet enough information. I'll post a separate
message about 
reporting debugger bugs right now.

Thanks,
Volodya

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

> > Oops, I got a crash when trying to unset a
breakpoint (the currently
> > debugged line was I believe the line on which the
breakpoint was):
> > Using host libthread_db library
"/lib64/libthread_db.so.1".
> > [Thread debugging using libthread_db enabled]
> > [New Thread 47913848629312 (LWP 4105)]
> > [New Thread 1082132800 (LWP 4126)]
> > [KCrash handler]
> > #5  0x0000000000000191 in ?? ()
> > #6  0x00002b93cf7f6121 in __dynamic_cast ()
>
> That's not yet enough information. I'll post a
separate message about
> reporting debugger bugs right now.
>
> Thanks,
> Volodya
>

I have looked at it a bit.. the crash happens in
Breakpoint::handleDeleted or 
or similar.. the problem is that before that is called, the
breakpoint is 
already deleted by a Qt-event. (deleteLater?).

Maybe you should think about using KSharedPtr or something..
that messing 
around with raw pointers looks dangerous and maybe isn't
necessary with 
high-level-stuff like Breakpoints 

greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

>
> > Oops, I got a crash when trying to unset a
breakpoint (the currently
> > debugged line was I believe the line on which the
breakpoint was):
> > Using host libthread_db library
"/lib64/libthread_db.so.1".
> > [Thread debugging using libthread_db enabled]
> > [New Thread 47913848629312 (LWP 4105)]
> > [New Thread 1082132800 (LWP 4126)]
> > [KCrash handler]
> > #5  0x0000000000000191 in ?? ()
> > #6  0x00002b93cf7f6121 in __dynamic_cast ()
>
> That's not yet enough information. I'll post a
separate message about
> reporting debugger bugs right now.
>

All you have to do to reproduce the crash is:
Start a debugging-session, set a breakpoint, jump to it, and
then delete it.

Btw. the new debugger-features are great, I can't wait
until they're ready 
usable 

greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

> All you have to do to reproduce the crash is:
> Start a debugging-session, set a breakpoint, jump to
it, and then delete
> it.
>
delete it by clicking the line at the left of the editor! I
don't know how it 
behaves if you delete it elsewise.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On Monday 22 May 2006 10:33, David Nolden wrote:
> > All you have to do to reproduce the crash is:
> > Start a debugging-session, set a breakpoint, jump
to it, and then delete
> > it.
>
> delete it by clicking the line at the left of the
editor! I don't know how
> it behaves if you delete it elsewise.

Thank you! I got this sporadic crash before, but never could
reproduce it 
afresh -- seems that it really happens only when clicking on
the marker in 
the editor.

This looks easy -- KDevelop sends two -break-delete commands
for the same 
breakpoint, and when response from the second arrives the
breakpoint object 
no longer exists.

Working on a fix...

- Volodya

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

> The thing is that when say, looking at pointer values,
fixed font is
> *much*
> better (IMO). And use smaller font size can make things
unreadable. I'm at
> loss.

I don't know, i never had problems before, but now it's a
real waste of
space.

>> Oops, I got a crash when trying to unset a
breakpoint (the currently
>> debugged line was I believe the line on which the
breakpoint was):
>> Using host libthread_db library
"/lib64/libthread_db.so.1".
>> [Thread debugging using libthread_db enabled]
>> [New Thread 47913848629312 (LWP 4105)]
>> [New Thread 1082132800 (LWP 4126)]
>> [KCrash handler]
>> #5  0x0000000000000191 in ?? ()
>> #6  0x00002b93cf7f6121 in __dynamic_cast ()
>
> That's not yet enough information. I'll post a
separate message about
> reporting debugger bugs right now.

It's enough to reproduce.  I
verified, it's when unsetting a breakpoint
of the currently debugged line. So set a breakpoint, run the
application,
when the application stops at the breakpoint unset it. It
should crash.

Andras

-- 
Quanta+ developer - http://quanta.kdewebdev.o
rg
K Desktop Environment - http://www.kde.org

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On Monday 22 May 2006 10:33, David Nolden wrote:
> > All you have to do to reproduce the crash is:
> > Start a debugging-session, set a breakpoint, jump
to it, and then delete
> > it.
>
> delete it by clicking the line at the left of the
editor! I don't know how
> it behaves if you delete it elsewise.

Fixed in revision 543556.

- Volodya

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel