>Marc-Andre Laperle
>Sent: Friday, April 09, 2010 12:23 PM
>To: CDT General developers list.
>Subject: Re: [cdt-dev] Possible to use the
>qtc-debugging-helper (Either DSF/CDI)
>
>I could give the TCF agent a shot for 7.1/8.0, but I feel that
>contributing to a third debugger will be counter productive. I
>want to help with what's best for the users. DSF-GDB works
>well on Mac with version 7.0 and CDI is also pretty good so I
>think it's tempting to maintain it for a while. What's the
>plan for EDC? Would it replace DSF-GDB as the primary debugger
>some day? Would a Mac agent benefit a product outside CDT ?
>I'm trying to prioritize here.
>
>Speaking of prioritizing, I think CDT 7.1/8.0 needs a clear
>plan early on. If CDT wants to be an end-user IDE, it has to
>bring back a balance between the what the companies and
>end-users want. The summit will be great for CDT as a platform
>but there should be more input from end-users. A mailing list
>and bugzilla are hardly a good place for user input. I think a
>poll on the CDT site would be a good start. It could be
>advertised on Doug's blog (Planet Eclipse exposure) and Twitter, etc.
>
>It could be something like this:
>
>"What would you like to be the focus in the next major CDT release?
>Select up to 3 items.
>
>-Improvements to the UI, usability and user documentation
>-Integration with other build systems -Integration with other
>compilers and debuggers -More Refactorings and Source
>generation -More debugging features -Improvements to the build
>system -Improvements to the editor and source navigation
>-General bug fixes -More code analysis -Better APIs for CDT
>vendors -Better documentation in CDT code -Better performance
>-Better stability
>
>Please add some details to what you selected. For example, if
>you selected 'Integration with other build systems', please
>specify which build systems.
><a text area>"
>
>What do you think?
>
>Marc-Andre
>
>On 10-04-09 11:37 AM,
Warren.Paul@xxxxxxxxx wrote:
>> As I said, our team will add Qt support to the EDC
>formatter, so the only missing piece for you then would be the
>Mac TCF agent. I'm not sure if anyone has considered writing
>such an agent yet or not, but this is probably the right forum
>to ask the question. :) I'm not a Mac guy so I can't say how
>much work that would be, but if the OS has any debug support
>(run control, memory/register access, breakpoints, etc), it
>shouldn't be too much effort.
>>
>> Thanks,
>> Warren
>>
>>
>>
>>> -----Original Message-----
>>> From:
cdt-dev-bounces@xxxxxxxxxxx
>>> [mailto:
cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of ext
>Michael Jackson
>>> Sent: Friday, April 09, 2010 10:06 AM
>>> To: CDT General developers list.
>>> Subject: Re: [cdt-dev] Possible to use the qtc-debugging-helper
>>> (Either DSF/CDI)
>>>
>>> Thanks for the info. At _some_ level it would seem to be
>possible to
>>> add the functionality (even if it is a plugin of some
>kind). It would
>>> seem that the qtc-debugging-helper library sends back a
>response to a
>>> gdb request for the "value"
>>> or maybe the QtCreator gdb wrapper figures out that the
>user wants to
>>> look at a QString and then asks the library to dump the values and
>>> such based on the pointer? Dunno. Can't really follow along. I may
>>> inquire on the QtCreator Mailing list garner some more info.
>>>
>>> --
>>> Mike Jackson<
www.bluequartz.net>
>>>
>>> On Apr 9, 2010, at 10:36 AM,<
Warren.Paul@xxxxxxxxx> wrote:
>>>
>>>
>>>> We've designed a powerful variable formatter in EDC which does the
>>>> basics like being able to change the display in the details
>>>>
>>> pain, but
>>>
>>>> also optionally allowing the children of the variable to be
>>>>
>>> changed as
>>>
>>>> well. It also will allow (not fully implemented yet)
>modifying the
>>>> value in formatted form. We will have support for Qt
>types in this
>>>> solution (also not yet implemented).
>>>>
>>>> Unfortunately I don't think this does much to help you out
>since EDC
>>>> doesn't currently work on Mac, only Windows and Linux. It
>would be
>>>> great to have someone do a TCF debug agent on Mac though.
>:) Maybe
>>>> you can focus your time on that and we'll provide the Qt
>formatting
>>>> aspect?
>>>>
>>>> I should mention that we really wanted to and tried to make this
>>>> feature non-EDC specific, but there were some technically
>>>>
>>> reasons why
>>>
>>>> it wouldn't work that I can't recall right now. :) It may be that
>>>> only some of it is EDC specific, I'm not sure. David Dubrow might
>>>> chime in if he's listening.
>>>>
>>>> Thanks,
>>>> Warren
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From:
cdt-dev-bounces@xxxxxxxxxxx
>>>>> [mailto:
cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of ext
>>>>>
>>> Michael Jackson
>>>
>>>>> Sent: Friday, April 09, 2010 9:20 AM
>>>>> To: CDT General developers list.
>>>>> Subject: Re: [cdt-dev] Possible to use the qtc-debugging-helper
>>>>> (Either DSF/CDI)
>>>>>
>>>>> I forgot to mention that I am on "that troublesome platform, OS X"
>>>>> where the only GDB that seems to work is the one from Apple
>>>>>
>>> which is
>>>
>>>>> like version 6.3 or something like that so using the
>Python Pretty
>>>>> Printers will not work for this particular platform.
>>>>>
>>>>> Now obviously since QtCreator does this sort of thing DSF
>>>>>
>>> GDB should
>>>
>>>>> be able to be made to do it also. I just have absolutely NO idea
>>>>> where I would start looking. Even a hacked together proof
>>>>>
>>> of concept
>>>
>>>>> would motivate me to spend some late nights getting something
>>>>> together.
>>>>>
>>>>> --
>>>>> Mike Jackson<
www.bluequartz.net>
>>>>>
>>>>> On Apr 9, 2010, at 10:13 AM, Elmenthaler, Jens wrote:
>>>>>
>>>>>
>>>>>> If you use gdb, you might want to check the python
>pretty printers
>>>>>> being supported by gdb 7.0 and later.
>>>>>>
>>>>>> It effectively means to translate your qtc-debugging-helper
>>>>>>
>>>>> library to
>>>>>
>>>>>> python pretty printers, but this might be valuable anyway.
>>>>>>
>>>>>> Both gdb integrations (DSF GDB would require the
>upcoming CDT 7.0)
>>>>>> have basic support for the pretty printers. Basic support
>>>>>>
>>> means the
>>>
>>>>>> info provided by the pretty printers appears in the
>>>>>>
>>> details pane of
>>>
>>>>>> variables and expressions view. But the children and
>>>>>>
>>>>> variables are not
>>>>>
>>>>>> the ones provided by the pretty printers.
>>>>>>
>>>>>> I'm working on fully enabling them in the variables and
>>>>>>
>>> expressions
>>>
>>>>>> view (bug302121). That, however, will only work in DSF GDB.
>>>>>>
>>>>>> Jens.
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:
cdt-dev-
>>>>>>>
bounces@xxxxxxxxxxx] On Behalf Of Michael Jackson
>>>>>>> Sent: Freitag, 9. April 2010 16:04
>>>>>>> To: CDT General developers list.
>>>>>>> Subject: [cdt-dev] Possible to use the
>>>>>>>
>>> qtc-debugging-helper (Either
>>>
>>>>>>> DSF/CDI)
>>>>>>>
>>>>>>>
>>>>>>> I do a bunch of Qt programming and I prefer to use
>>>>>>>
>>> Eclipse CDT to
>>>
>>>>>>> do my programming. The major hurdle that I have currently
>>>>>>>
>>>>> is trying
>>>>>
>>>>>>> to
>>>>>>> debug Qt based code. Due to the design of the Qt classes when
>>>>>>> trying to get the "value" of things like a QString gdb will just
>>>>>>>
>>>>> send back a
>>>>>
>>>>>>> pointer address that isn't really helpful. With Qt-Creator the
>>>>>>> engineers at Nokia have implemented the qtc-debugging-helper
>>>>>>> library which your project can link against.
>>>>>>>
>>>>>>> What I was wondering would be what type of code
>updates to CDT
>>>>>>> (Either in CDI or DSF) would have to go into place in oder to
>>>>>>> effectively use the code contained in the qtc-debugging-helper
>>>>>>> library? Looking through the qtc-debugging-helper library
>>>>>>>
>>> it seems
>>>
>>>>>>> there are "pretty-printers" for the Qt Classes which
>can then be
>>>>>>> piped back to the IDE making the request to display
>more helpful
>>>>>>> values of a class rather then the internal pointer.
>>>>>>>
>>>>>>> I am motivated enough to start hacking in CDT to at least
>>>>>>> figure out if this type of thing is even possible. Even better
>>>>>>>
>>>>> would be some
>>>>>
>>>>>>> help from Nokia to point me in the right direction ;-) ***
>>>>>>>
>>>>>>> Thanks
>>>>>>> ___________________________________________________________
>>>>>>> Mike Jackson
www.bluequartz.net
>>>>>>> Principal Software Engineer
mike.jackson@xxxxxxxxxxxxxx
>>>>>>> BlueQuartz Software Dayton, Ohio
>>>>>>>
>>>>>>> *** I know this is basically helping out a rival product
>>>>>>>
>>>>> (QtCreator
>>>>>
>>>>>>> vs
>>>>>>> Eclipse CDT) but I think would still be seen as a
>Win-Win for all
>>>>>>> parties.
>>>>>>> _______________________________________________
>>>>>>> cdt-dev mailing list
>>>>>>>
cdt-dev@xxxxxxxxxxx
>>>>>>>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>>>
>>>>>> _______________________________________________
>>>>>> cdt-dev mailing list
>>>>>>
cdt-dev@xxxxxxxxxxx
>>>>>>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>>
>>>>> _______________________________________________
>>>>> cdt-dev mailing list
>>>>>
cdt-dev@xxxxxxxxxxx
>>>>>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>> _______________________________________________
>>>>>
>>>> cdt-dev mailing list
>>>>
cdt-dev@xxxxxxxxxxx
>>>>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>
>>> _______________________________________________
>>> cdt-dev mailing list
>>>
cdt-dev@xxxxxxxxxxx
>>>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>> _______________________________________________
>>>
>> cdt-dev mailing list
>>
cdt-dev@xxxxxxxxxxx
>>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>_______________________________________________
>cdt-dev mailing list
>
cdt-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
>_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev