Delay in GDB

[Kishore Jonnalagadda]

On Aug 25, 2011 11:07 PM, "Niko Sams" <niko.sams at gmail.com> wrote:
>
> Hm, sounds like a ugly workaround that only works if you move the mouse
> fast enough...
> Isn't it possible to fix the real cause for the error?
> What is a "bus error" - who causes this error?

(I assume the request to gdb is being made by the tooltip)
I think it is a good idea to delay the gdb request/tooltip independent of
the proper fix.

> Niko
>
> On Tue, Aug 23, 2011 at 19:08, Leon Pollak <leonp at plris.com> wrote:
> > Hello, all.
> >
> > I am working with the embedded linux (remote debugging) and encounter
the
> > following problem: some variables/elements in the program under
debugging can
> > not be displayed by the gdb/gdbserver and cause the "bus error".
> > Such are, for example, mapped memory locations, errno variable and some
more.
> > Kdevelop today has a brilliant feature - display the variable value when
the
> > cursor hoovers over it. The problem is, that it tries to do this
immediately!
> > This means, that even when one passes through this 'problematic'
variable on
> > his way to 'normal' variable, it causes the bus error.
> >
> > So, what I ask is some, let's say, 0.5-1s delay between the STOP over
the
> > variable and the request to the gdb to show it.
> >
> > Many thanks ahead.
> > --
> > Leon.
> >
> > _______________________________________________
> > kdevelop mailing list
> > kdevelop at kdevelop.org
> > https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop
> >
>
> _______________________________________________
> kdevelop mailing list
> kdevelop at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110826/86cda5f9/attachment.html>