Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Mac debug needs attention (patches are available!)

I'll see what I can add to the bug reports. That was a great example
of the OS X community working in harmony with the Eclipse developers
to get a patch put into CVS. Took a bit longer than some of us were
hoping but it finally did get there.
  I guess I am getting more vocal as I don't want at least the
critical bugs to be left out of CDT 7.0. At that point I think most in
the OS X Community would probably give up and move to something like
QtCreator, but that is just a guess.

Mike Jackson                  mike.jackson@xxxxxxxxxxxxxx

On Mon, Jan 4, 2010 at 9:35 PM, Marc-Andre Laperle
<malaperle@xxxxxxxxxxxxx> wrote:
> Thank you Mike for your time and feedback. Would you mind adding the
> comments in Bugzilla? We can continue the discussion on individual bugs
> there.
> I was also hoping for some attention from committers. Anyone? I think it
> would be possible for a committer to fix the bugs even without a Mac with
> proper code review and testing from the community. This has been done
> successfully in bug 270790 thanks to Andrew and the help of users with Macs.
> Maybe we could do this again but this time, we need the help of a "debug
> committer".
> Marc-Andre
> On 1/4/2010 3:12 PM, Michael Jackson wrote:
>> On Jan 4, 2010, at 1:31 PM, Marc-Andre Laperle wrote:
>>> Hello all,
>>> As you might know, debugging on Mac is not in a very good state. It has
>>> been said that the community would need to fix these issues since the
>>> majority a committers don't have a Mac. So, I made patches for the following
>>> bugs:
>>> - Debug value view fails to update 'Value' column (250037), also fixes
>>> the same bug in DSF
>>> - [Mac] Debug launch takes 20 extra sec (CLI problem) (294538)
>>> - [Mac] Registers view very slow to open the first time (294537)
>>> - GDB can't halt debugging process (265483)
>>> - CDT gdb/mi fails to parse result of gdb cmd "thread info" (269838)
>>> It would be great if someone could take a look at these patches and at
>>> least give some feedback. I won't be available tomorrow for the CDT Monthly
>>> Call so if someone can bring it up, I would be grateful.
>>> Thanks!
>>> Marc-Andre
>> Cursory testing of the patch included with bug 265483 shows that I can
>> indeed set more break points and have CDT stop the program at those new
>> break points that were set _after_ the program was already being debugged.
>> _________________________________________________________
>> Mike Jackson                  mike.jackson@xxxxxxxxxxxxxx
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx

Back to the top