GDB debugger working style questions.

I want to clear the appreance and GUI for gdb plugin in
KDev4.

1. supporting multiple project simultaneously

Should we allow debugging more than 2 project
simultaneously?
I don't think so. Multiple debugger running only confuses
user, and
it will lead to much more complexity in architecture while
gaining
very little benefit.

2. GDB output views.

a)
In KDev3, gdb output widgets such as framestack, variable
displayer
were displayed only when gdb is being run. After gdb
finished, these
display widgets were hidden.
Now, in current sublime UI, is it possible that gdb part
can
hide/show its own widgets anytime when he wants?

b)
Do we need to allow multiple gdb views? Specifically, it
doesn't
make sense to have 3~5 breakpoint displayers for one
project. Rather
I think we need to restrict the number of breakpoint view
just "one"
for each project.

3. Shortcut to start debugger.

There is no concept of "active project" in Kdev4.
Now the user
presses F9, how does the gdb know which project to start?

4. Gdb plugin path.

In kdev3, gdb is under languages/cpp/debugger. But gdb is
not designed
only for C. Fortran and other languages can use gdb. I
suggest
plugin/gdb as its path.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Thursday 21 Jun 2007 12:48:50 am dukju ahn wrote:
> I want to clear the appreance and GUI for gdb plugin in
KDev4.
>
> 1. supporting multiple project simultaneously
>
> Should we allow debugging more than 2 project
simultaneously?
> I don't think so. Multiple debugger running only
confuses user, and
> it will lead to much more complexity in architecture
while gaining
> very little benefit.
>
> 2. GDB output views.
>
> a)
> In KDev3, gdb output widgets such as framestack,
variable displayer
> were displayed only when gdb is being run. After gdb
finished, these
> display widgets were hidden.
> Now, in current sublime UI, is it possible that gdb
part can
> hide/show its own widgets anytime when he wants?
>
> b)
> Do we need to allow multiple gdb views? Specifically,
it doesn't
> make sense to have 3~5 breakpoint displayers for one
project. Rather
> I think we need to restrict the number of breakpoint
view just "one"
> for each project.
>
> 3. Shortcut to start debugger.
>
> There is no concept of "active project" in
Kdev4. Now the user
> presses F9, how does the gdb know which project to
start?
>
> 4. Gdb plugin path.
>
> In kdev3, gdb is under languages/cpp/debugger. But gdb
is not designed
> only for C. Fortran and other languages can use gdb. I
suggest
> plugin/gdb as its path.

When this is being worked upon, would it be possible to add
a registers view 
where one can see and set the values of processor registers?
This would 
benefit those of us using KDevelop for cross-development.
-- 
Cheers!
kitts

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 20.06.07 15:18:50, dukju ahn wrote:
> I want to clear the appreance and GUI for gdb plugin in
KDev4.
> 
> 1. supporting multiple project simultaneously
> 
> Should we allow debugging more than 2 project
simultaneously?
> I don't think so. Multiple debugger running only
confuses user, and
> it will lead to much more complexity in architecture
while gaining
> very little benefit.

I'm not so sure about that. It certainly is easier to
implement, but why
do I need to quit debugging application foo, just to check
some minor
thing on application bar?

> 2. GDB output views.
> 
> a)
> In KDev3, gdb output widgets such as framestack,
variable displayer
> were displayed only when gdb is being run. After gdb
finished, these
> display widgets were hidden.
> Now, in current sublime UI, is it possible that gdb
part can
> hide/show its own widgets anytime when he wants?

No, but IIRC Alexander agreed to provide that functionality.
All we have
at the moment is removeToolView.

> b)
> Do we need to allow multiple gdb views? Specifically,
it doesn't
> make sense to have 3~5 breakpoint displayers for one
project. Rather
> I think we need to restrict the number of breakpoint
view just "one"
> for each project.

There's no API for that, and AFAIK Alexander is very much
against
providing such API. 

> 3. Shortcut to start debugger.
> 
> There is no concept of "active project" in
Kdev4. Now the user
> presses F9, how does the gdb know which project to
start?

The user doesn't press F9  Well
actually that's something we need to
solve in a more general way.

> 4. Gdb plugin path.
> 
> In kdev3, gdb is under languages/cpp/debugger. But gdb
is not designed
> only for C. Fortran and other languages can use gdb. I
suggest
> plugin/gdb as its path.

Actually I'd rather see a more general debug/run framework
in
kdevplatform, with gdb implementing it for certain types of
binaries/languages. I haven't thought about that too much,
IIRC Volodya
had some ideas on how to do that, but he's been largely
"away" lately.

Andreas

-- 
Your love life will be... interesting.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

kitts wrote:
> When this is being worked upon, would it be possible to
add a registers view 
> where one can see and set the values of processor
registers? This would 
> benefit those of us using KDevelop for
cross-development.

Hmm, considering MSVC has had a registers view since 6.0
(which is, 
what, pushing ten years old?), that sounds like a good idea.


-- 
Matthew
"Nobody expects the Spanish Inquisition!" -- Monty
Python


_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Thursday 21 June 2007 02:31, Matthew Woehlke wrote:
> kitts wrote:
> > When this is being worked upon, would it be
possible to add a registers view 
> > where one can see and set the values of processor
registers? This would 
> > benefit those of us using KDevelop for
cross-development.
> 
> Hmm, considering MSVC has had a registers view since
6.0 (which is, 
> what, pushing ten years old?), that sounds like a good
idea. 

That's kinda planned. I actually have register view for a
specific
processor for KDevelop 3.4, but never had change to design
minimally
generic UI for that.

- Volodya

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Wednesday 20 June 2007 23:49, Andreas Pakulat wrote:
> > 3. Shortcut to start debugger.
> > 
> > There is no concept of "active project"
in Kdev4. Now the user
> > presses F9, how does the gdb know which project to
start?
> 
> The user doesn't press F9  Well
actually that's something we need to
> solve in a more general way.

When the user presses F9, debugger should launch the default
debugger
configuration, which is typically the last debugger
configuration launched.
There's no need, I think, to tie debugger configuration with
projects --
you can decide to debug random binary on your disk.

> > 4. Gdb plugin path.
> > 
> > In kdev3, gdb is under languages/cpp/debugger. But
gdb is not designed
> > only for C. Fortran and other languages can use
gdb. I suggest
> > plugin/gdb as its path.
> 
> Actually I'd rather see a more general debug/run
framework in
> kdevplatform, with gdb implementing it for certain
types of
> binaries/languages. I haven't thought about that too
much, IIRC Volodya
> had some ideas on how to do that, but he's been largely
"away" lately.

I actually don't have good ideas for *that*. I'd imagine
that fortran
will need some specific logic, not to mention ada (that gdb
also supports),
and I don't know the best way to handle that yet.

What we surely might have, is a set of basic debugger
widgets, however, to be reused by
specific debugger types.

- Volodya

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 21.06.07 08:46:51, Vladimir Prus wrote:
> On Wednesday 20 June 2007 23:49, Andreas Pakulat
wrote:
> > > 3. Shortcut to start debugger.
> > > 
> > > There is no concept of "active
project" in Kdev4. Now the user
> > > presses F9, how does the gdb know which
project to start?
> > 
> > The user doesn't press F9  Well
actually that's something we need to
> > solve in a more general way.
> 
> When the user presses F9, debugger should launch the
default debugger
> configuration, which is typically the last debugger
configuration launched.
> There's no need, I think, to tie debugger configuration
with projects --
> you can decide to debug random binary on your disk.

Right, I didn't think long enough about the answer... 

> > > 4. Gdb plugin path.
> > > 
> > > In kdev3, gdb is under
languages/cpp/debugger. But gdb is not designed
> > > only for C. Fortran and other languages can
use gdb. I suggest
> > > plugin/gdb as its path.
> > 
> > Actually I'd rather see a more general debug/run
framework in
> > kdevplatform, with gdb implementing it for certain
types of
> > binaries/languages. I haven't thought about that
too much, IIRC Volodya
> > had some ideas on how to do that, but he's been
largely "away" lately.
> 
> I actually don't have good ideas for *that*. I'd
imagine that fortran
> will need some specific logic, not to mention ada (that
gdb also supports),
> and I don't know the best way to handle that yet.
> 
> What we surely might have, is a set of basic debugger
widgets, however, to be reused by
> specific debugger types.

And a way to specify how a program is run/debugged is also
needed. So
some API and storage of debug/run-configurations is needed.

Andreas

-- 
Write yourself a threatening letter and pen a defiant
reply.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 6/20/07, dukju ahn <dukjuahngmail.com> wrote:
> I want to clear the appreance and GUI for gdb plugin in
KDev4.
> 1. supporting multiple project simultaneously

Ok, I do think we need to support that but the only possible
UI for
that is to open new mainwindow in "debugger" area
for each binary
being debugged inside KDevelop. This is what we decided upon
last
aKademy and this is what sublime allows you to do.

> 2. GDB output views.
> Now, in current sublime UI, is it possible that gdb
part can
> hide/show its own widgets anytime when he wants?
I'll implement that tomorrow.


> 4. Gdb plugin path.
>
> In kdev3, gdb is under languages/cpp/debugger. But gdb
is not designed
> only for C. Fortran and other languages can use gdb. I
suggest
> plugin/gdb as its path.

plugins/gdbdebugger ?

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Wednesday 20 June 2007, Andreas Pakulat wrote:
> I'm not so sure about that. It certainly is easier to
implement, but
> why do I need to quit debugging application foo, just
to check some
> minor thing on application bar?

Of course if we support multiple projects, makes sense to
support 
debugging of them. But good luck to start the debugger twice
on two kde 
projects. 


Andras

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


_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 03.07.07 00:13:44, Andras Mantia wrote:
> On Wednesday 20 June 2007, Andreas Pakulat wrote:
> > I'm not so sure about that. It certainly is easier
to implement, but
> > why do I need to quit debugging application foo,
just to check some
> > minor thing on application bar?
> 
> Of course if we support multiple projects, makes sense
to support 
> debugging of them. But good luck to start the debugger
twice on two kde 
> projects. 

Why should that be a problem? Eclipse does that pretty well
and gdb
itself surely has no problem starting two kde apps at the
same time.

Or did I (again) miss the punchline?

Andreas

-- 
The whole world is a tuxedo and you are a pair of brown
shoes.
		-- George Gobel

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel