X-Spam-Check-By: sourceware.org Message-ID: <4487ECCD.747EC55A@dessent.net> Date: Thu, 08 Jun 2006 02:24:29 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Gdb and debug symbol in pdb References: <1135171526 DOT 20060608115104 AT mail DOT ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Sergey Tovpeko wrote: > I've a question about using gdb on windows. I'm debugging a > program produced by Microsoft compiler. It would be nice of GDB > to understand debug symbols in Microsoft-specific debug format (PDB). > Did anyone try to support this format in gdb? I know, it's private. > But Microsoft provides a big API for analyzing pdb format. No, to my knowledge no one has ever tried to support PDB format in gdb. It sounds like an extremely non-trivial undertaking. It would not just be a matter of reading an undocumented file format. Gdb would have to be taught all the details of the MSVC C++ ABI -- name mangling, vtable layout, and so on. I suppose you could just support C only, but that would make it useless for a great deal of code. And on top of that the people who develop gdb are also those who probably have the least desire to use MS proprietary compilers, as they tend to have a stake in the gnu toolchain anyway. Besides, there are already plenty of debuggers that understand PDB, both Microsoft and third party, so it would be reinventing a wheel. You might want to have this discussion on the gdb list, though I'm sure it's come up before. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/