[cdt-debug-dev] RE: Applying patches

[Alain Magloire <alain@xxxxxxx>]

> 
> >  Bonjour,
> >
> >   Folks,  a bunch of outstanding patches were in the backlog, I help
> clean a
> >  little, thanks to Elena:
> >
> >  bugs
> >  219863 nor P3 Wind ken.ryall@xxxxxxxxx ASSI regression: Address
> breakpoints
> >  inserted from console do not resolve location properly
> >  218260 nor P3 Wind cdt-debug-inbox@xxxxxxxxxxx NEW Performance issues
> while
> >  stepping through with many threads
> >  221944 nor P3 Wind cdt-debug-inbox@xxxxxxxxxxx NEW Cannot display long
> long
> >  int as hex
> >
> >  features
> >  220045 nor P3 Wind cdt-debug-inbox@xxxxxxxxxxx NEW Debuger is stopping
> on
> >  non-existing breakpoints for files with same name
> >  221408 nor P3 Wind cdt-debug-inbox@xxxxxxxxxxx NEW Ability to move
> >  breakpoints manually to a different line
>

Bonjour O:yvind,
 
> Merci!
> 

It should go to Elena.

> I'm just wondering: why is there so little activity on the CDT
> GDB implementation?
>

Mea culpa, I have been quite busy.
 
> There are a fair number of "trivial" fixes like the above that will
> make a *big* difference.
> 
> E.g. this bug is serious enough that it should have seen activity if
> there was anyone at all working full time on CDT GDB:
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=208984
> 

In this case, is this the right approach?  The reason we use the process
factory class it because it allow us some flexibility, like being able to
send different signal to the process.  It is not possible to do it with
Runtime.exec.

It is something that you see only in your environment or a general problem?
I can see ProcessFactory taking sometimes since it needs to load a dll, the
code is implemented via JNI, but 10 seconds, seem like an awfully long
time...



> --
> Øyvind Harboe
> http://www.zylin.com - eCos ARM & FPGA developer kit