Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] FW: Fixing some Debug feature-parity bugs

+1 for nuking... or just use conventional weapons to avoid international scrutiny

Seriously though, cdt-debug-dev hasn't been used in years and its presence only creates confusion.


Doug Schaefer wrote:
That's a good point. cdt-debug-dev was one of our old mailing lists. A while ago to help build community momentum I recommended that we scrap the other ones that were there to get more topics on the cdt-dev list for all to see. We left cdt-debug-dev, but I can't remember why other than volume issues.

I'd still like to keep everything on the one list, should we nuke cdt-debug-dev or do people still fine it valuable to have.


On Mon, Feb 8, 2010 at 2:21 PM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:
(Forwarded from cdt-debug-dev, sorry again for the confusion I caused)
Some DSF doc Pawel just checked-in

-----Original Message-----
From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech
Sent: Monday, February 08, 2010 1:14 PM
To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] Fixing some Debug feature-parity bugs

Marc-Andre Laperle wrote:
> I will also look at any bugs on Mac that might come up. Maybe we
> should have a wiki page with who is trying to fix what? Also, is there
> any documentation on DSF/DSF-GDB that could help me getting more
> familiar with the framework?
I've recently updated the DSF tutorial from EclipseCon 2008 and I've
been meaning to add it to the CDT documentation.  I went ahead and added
it with bug 302175.

You should be able to look at it from CVS under, or
get the nighly build tomorrow and search for DSF in the help page.

cdt-debug-dev mailing list
cdt-dev mailing list

_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx

Back to the top