Re: Porting gdb debugger in KDev4

On Thursday 28 June 2007 19:05, dukju ahn wrote:
> Hi. I'm dukju, one of the kdevelop new developer.
> 
> I'm currently working on porting gdb debugger in KDev4.
My plan is
> just porting and readjustment to new qt4/kde4/kdevelop4
environment,
> not modifying the core logic of gdb. Only after porting
is completed,
> any new bugfixes, additions can be taken place.
> 
> But, I'm worried that you are also working gdb
currently. In that case,
> it's a duplication of effort -- a bad situation. So I'd
like to check
> the progress
> each other. Currently, I didn't do much job, but I have
full free vacation
> for the entire july.

Hi dukju,

First of all, thanks for the offer, it's much appreciated. 
To answer your question, I haven't done any practical
porting of debugger as yet.

I was thinking that a change in architecture is required,
and it's probably better
to do that change when porting to KDevelop4, so avoid fixing
possible bugs in 
a code that will be much simpler with the right
architecture. Unfortunate, said
architecture is not finished yet.

I suppose we can discuss said architecture together.
I also think a help when porting to the new architecture
will be very valuable.
Doing 1<->1 port of the current architecture to
KDevelop4 will also be
helpful, but in this case I'm afraid a lot will have to be
reworked.

What do you think?

- Volodya

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

2007/6/29, Vladimir Prus <ghostcs.msu.su>:
> On Thursday 28 June 2007 19:05, dukju ahn wrote:
> > Hi. I'm dukju, one of the kdevelop new developer.
> >
> > I'm currently working on porting gdb debugger in
KDev4. My plan is
> > just porting and readjustment to new
qt4/kde4/kdevelop4 environment,
> > not modifying the core logic of gdb. Only after
porting is completed,
> > any new bugfixes, additions can be taken place.
> >
> > But, I'm worried that you are also working gdb
currently. In that case,
> > it's a duplication of effort -- a bad situation.
So I'd like to check
> > the progress
> > each other. Currently, I didn't do much job, but I
have full free vacation
> > for the entire july.
>
> Hi dukju,
>
> First of all, thanks for the offer, it's much
appreciated.
> To answer your question, I haven't done any practical
porting of debugger as yet.
>
> I was thinking that a change in architecture is
required, and it's probably better
> to do that change when porting to KDevelop4, so avoid
fixing possible bugs in
> a code that will be much simpler with the right
architecture. Unfortunate, said
> architecture is not finished yet.
>
> I suppose we can discuss said architecture together.
> I also think a help when porting to the new
architecture will be very valuable.
> Doing 1<->1 port of the current architecture to
KDevelop4 will also be
> helpful, but in this case I'm afraid a lot will have to
be reworked.

I didn't know the renewal plan. In that case, doing 1:1 port
of current
structure doesn't have that much value.  I'll stop that
porting.

I will help the architecture renewal. I have full free time
for the entire july, but what I'm worried is that I can't
use my private
computer as of August -- I leave to other region of country.
From
august, I guess I can't participate KDevelop development. So
I
planned "as is" porting within july.

Please share any effort of architecture renewal to list.
I'll try to
help at least july.

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