Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] CDT launches (no longer) affected by DSF launches

Again, for those that install both DSF and CDT launches:,
has been fixed with a better solution than I expected.
The CDT launches will not be impacted at all by the DSF ones.
For those that care, you'll need DSF RC4 (or HEAD from this morning.)
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]On Behalf Of Marc Khouzam
Sent: Thursday, June 05, 2008 12:23 PM
To: DD DEV (E-mail); cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] CDT launches affected by DSF launches

For those of you that install both DSF and CDT launches, I made a boo-boo.
As part of bug 232357,
we removed all dependencies from DSF to the CDT Debug feature.
To achieve this, I used some of the CDT extension points to re-use CDT
code that is part of the CDT platform feature.
I just noticed that these extensionsalso get picked up  (of course) by the CDT
launches.  What that means is that if you have both DSF and CDT launches,
the CDT launches will contain two similar debugger entries:
gdb/mi twice
gdbserver debugger twice
One of these two choices is for DSF and will *not* work when used from a
CDT launch.
Bug 235862 has been opened about this.
The short term solution is to rename the DSF extensions labels to something
that will differentiate from the CDT ones like "gdb/mi (DSF only)"
Better solutions are welcome.
In the long term, Doug S wants to rework the whole launch framework, so this will
get fixed in the process.
My apologies for this poor interaction between DSF and CDT.


Marc Khouzam
Software Designer, Methods and Tools


Ericsson Canada Inc

8500 Decarie Blvd.
H4P 2N2, Mont-Royal, Qc, Canada

Office: +1 514 345 7900 x42350
Fax: +1 514 345 6159
Mobile: +1 514 951 7191
Email: Marc.Khouzam@xxxxxxxxxxxx

Ce courriel est confidentiel et uniquement destiné à son ou ses destinataires. Il est défendu de le consulter, de l'utiliser, de le dévoiler ou de le diffuser sans autorisation. Si ce message vous est parvenu par erreur, merci d'en aviser l'expéditeur par retour de courrier et de le détruire sans le divulguer.  Un courriel et ses pièces jointes peut être sans autorisation corrompu, interrompu, amendé, altéré et infecté. L'entreprise ne reçoit et n'envoie de courriel qu'avec l'entente qu'elle n'est responsable d'aucune corruption, interception, modification, altération, infection ou conséquence possible.

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.  E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


Back to the top