[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Embedded toolsets
|
>
> On Mon, 2003-01-20 at 22:22, Mikhail Khodjaiants (QNX) wrote:
> > > It is probably trying to set auto-solib on or off
> > >
> > > (gdb)
> > > 4-gdb-set auto-solib-add on
> > > 4^done off
> > >
> > > depending on your settings in the debugger path. And I guess, it fails.
>
> Spot on.
>
> 5-gdb-set auto-solib-add off
> &"No symbol \"auto\" in current context.\n"
> 5^error,msg="No symbol \"auto\" in current context."
> (gdb)
>
> > > Not sure what the best policy ... removing of this option?
> > > Ignoring the error and keep on going ?
> > >
> >
> > I think we should display a warning.
>
> Perhaps it would be best to only display this warning if we had
> attempted to turn auto-solib on?
>
Well it is a GNU/linux local launcher and when the setting fails it is an error.
For example, Doug @ rationale, did the Cygwin local launcher, and it does
not try to set the "auto-solib-path" because there no such thing in
the Cygwin gdb environment(at least the one in the head).
We can certainly makes things easier for by ignoring the error for now.
The CDT/Debug plan is very agressive(see other posting) but one thing is lacking
is the capability to provide (remote) targets. The idea was to provide
an extension point, where one could implement an ITargetProvider etc ..
The notion of "target" is a little fuzzy because it has to be tied with
the builder (cross-dev, building for a specific target), the debugger
(debugging a remote target, via serial/IP (gdbserver or other proxies)) and
other module within the CDT.
We are lacking time for this so I doubt the entire framework will be in
place for the next release ... but if you want to have a spin at it
I'll be happy to assist.
The "long term" vision is to have 3rd parties quickly come up with a plugin adapter
to enable there tools , so one can say "build and debug" for palm-pilot
without too much trouble.
> >From a user's point of view it would quickly become frustrating getting
> warnings every time we start a debug session if there was no means so
> suppress that warning.
>
Agree, dialog prompts are evil 8-)
