Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Fwd: Gdb behaviour breaking change

Well, we should really fix up our code to match. The proper way to do command line arguments is as an array of Strings. But Elena brings up a good point. It is an API breakage. A good one but it may break others who aren't paying as close attention.


From: Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>
Date: Tue Oct 07 2014 17:18:49 GMT-0400 (EDT)
To: elaskavaia.cdt@xxxxxxxxx <elaskavaia.cdt@xxxxxxxxx>, CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Cc: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Fwd: Gdb behaviour breaking change

Sorry about that.  I guess you need to keep compatibility with older versions of your code so you need CDT to keep calling the old method?



----- Original Message -----
From: Alena Laskavaia <elaskavaia.cdt@xxxxxxxxx>
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Sent: 07/10/2014 15:41
Subject: [cdt-dev] Fwd: Gdb behaviour breaking change

This change broke our debugger integration:

Bug 445360 - Can't debug when GDB path contains spaces.

We have our own debugger so we override getGDBCommandLine
function to have different path to gdb and params. This change introduced another function
which is called instead. Even API is not broken our function is not called anymore

so it does not work. Function is deprecated now, but it was not before this fix.

I think we should revert this fix and make it backward compatible

Back to the top