|XML IL firstname.lastname@example.org (Alex Colvin) (2001-08-15)|
|Re: XML IL email@example.com (jacob navia) (2001-08-17)|
|Re: XML IL firstname.lastname@example.org (Joachim Durchholz) (2001-08-17)|
|Re: XML IL email@example.com (Thomas Maslen) (2001-08-17)|
|Re: XML IL firstname.lastname@example.org (2001-08-18)|
|Date:||18 Aug 2001 00:43:21 -0400|
|Posted-Date:||18 Aug 2001 00:43:21 EDT|
jacob navia <email@example.com> wrote:
>I have incorporated XML into my resource editor. (lcc-win32) The next
>step is to generate XML to hold the browse information, and
>(eventually) all debug information.
A few of us here at Agere Systems (which used to be part of Bell Labs
which used to exist) who design & build embedded processing software
tools (especially debuggers & profilers) have started prototyping a
XML carrier for debug information that traditionally comes to a
debugger via DWARF (or similar). We get the target process state
information (which changes frqeuently) via a RPC mechanism against an
API (that could be standardized), we (are starting to) get debugging
symbolic info (which changes infrequently) via XML.
It seems to make sense, not only for portability among compilers, but
also for distributed debugging, cross debugging, etc., where the
debugger machine is different from the target.
Don't have any results yet. Would be interested in hearing similar
tales, pitfalls, etc.
Dale Parson, Consulting Member of Tech. Staff
Agere Systems, firstname.lastname@example.org
Return to the
Search the comp.compilers archives again.