|Re: [dsdp-dd-dev] Bugs for 1_1_maintenance|
Marc Khouzam wrote:
No, actually we're stretched pretty thin at the moment trying to complete features we need in CDT 6.0. I'm sorry about this, though it looks like it won't make much of a difference to you. In the project meta-data I'll just push out the proposed 1.1.1 release date way in the future in case we decide on it at some point.Hi, 1.1.1 was meant for GDB7.0 which is scheduled for June 5th. You are right that it is so close to CDT 6.0 that there is not much point. So I agree that we can stick to the 1.1 maintenance. As for doing an actual release, that would be nice if it means we'll do some testing to give it more stability. If we don't do that, then there is not much worth in doing an official release; we at Ericsson, can deal with checking out the plugins. So, do you guys have time for a bit of testing for an official 1.1 release, or should we just stick to the branch? On my side, I would have some time after eclipseCon.
Thanks-----Original Message----- From: dsdp-dd-dev-bounces@xxxxxxxxxxx [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech Sent: Wednesday, March 18, 2009 11:56 AM To: Device Debugging developer discussions Subject: Re: [dsdp-dd-dev] Bugs for 1_1_maintenance Hi Marc, If you prefer we could just wrap up the changes in 1.1 maintenance branch and push them out in a release. As we get closer to CDT 6.0 we have less and less motivation to generate a DD 1.1.1 release. -Pawel Marc Khouzam wrote:Hi, I just found out that we at Ericsson, will take a version of the R1_1_maintenance for an internal delivery on Monday the 9th of March. Therefore, I want to migrateany importantDSF/DSF-GDB bug fixes that were only done in the CDT. I already did these: http://bugs.eclipse.org/249227 [console][cdi] Add supportfor "verbose"tracing of MI commands in console http://bugs.eclipse.org/256663 [multi-process] Better handling of automatic attaching of a process http://bugs.eclipse.org/261883 [DsfMemoryBlock] Workerthreads leak inDsfMemoryBlock.writeMemoryBlock() http://bugs.eclipse.org/261406 [launch] IsConnected() wrongfor Localdebug session for 7_0 services http://bugs.eclipse.org/266741 [launch] Launch showsterminated even ifa launch process remains running http://bugs.eclipse.org/266599 [multi-process] Don't prompt for a process to attach to right after launch http://bugs.eclipse.org/261753 [event] Invalid MI event can cause NullPointerException http://bugs.eclipse.org/261082 [multi-process] Race condition when creating a breakpoint The ones I think should be done follow. All but the firstare in DSF.I'll do the work, but I'm looking for an OK, since it is DSF (not DSF-GDB) and that I didn't work on these bugs. http://bugs.eclipse.org/261258 [breakpoint] ClassCastException on breakpoint action http://bugs.eclipse.org/261384 DSF Details Pane does notpay attentionto its Max Length value http://bugs.eclipse.org/261858 [debug view] After suspendevent, onlythe top stack frame should be retrieved initially. http://bugs.eclipse.org/262210 There are caching issues with the DsfMemoryBlock http://bugs.eclipse.org/262245 [vm] AbstractVMProvider mayinstall thesame model proxy for multiple views, resulting in the viewer not working. http://bugs.eclipse.org/266105 Unable to see DSF disassembly Thanks a lot! Marc _______________________________________________ dsdp-dd-dev mailing list dsdp-dd-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev_______________________________________________ dsdp-dd-dev mailing list dsdp-dd-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev_______________________________________________ dsdp-dd-dev mailing list dsdp-dd-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
Back to the top