Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Gabe Black" <gabebblack@gmail.com>
To: gdb@sourceware.org
Subject: MSVC and DIA
Date: Fri, 22 Aug 2008 20:43:00 -0000	[thread overview]
Message-ID: <8a15eb2b0808220949vffa9aaqe2c4c635857d83d7@mail.gmail.com> (raw)

In a couple of other posts I alluded to debugging a target in which I
did not have symbol information.  The target is a custom RTOS running
on an i386 architecture built using different versions of the MSVC
compiler.  I've investigated using Visual Studio to debug the target
and even talked with MS but the amount of work to implement a
"Debugging Engine" to provide this facility is really not worth it.
Furthermore, Microsoft will not allow us to use WinDBG to debug on the
target as well since it isn't a "Windows" target (even though WinDBG
did work for us).

GDB seems like a viable alternative, and all that seems to be missing
is symbol interpretation.  Microsoft provides the Debug Interface
Access SDK (DIA) which I did not find referenced in any of the mailing
lists.  It is an SDK that allows you to get at any of the debug/symbol
information in a PDB even if the format of the PDB changes.  I would
like to add PDB symbol support to GDB.  I am fairly new to GDB but I
have been able to implement the remote stub running on the target
without much trouble.  However the challenge lies in adding the symbol
support.  From what I understand, BFD is where I would need to add the
PDB symbol support.  I didn't find much about it in the gdb online
documentation, both in the user manual and internal documentation.

Does anyone have any pointers or references of documentation/files to
look at to help me get started?  We've tasted the sweetness of using a
source-level debugger and we want more! Am I off my rocker in
attempting this?!

Thanks,
Gabe


             reply	other threads:[~2008-08-22 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 20:43 Gabe Black [this message]
2008-08-22 20:48 ` Stan Shebs
2008-08-25 16:41   ` Michael Snyder
2008-08-25 17:29     ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8a15eb2b0808220949vffa9aaqe2c4c635857d83d7@mail.gmail.com \
    --to=gabebblack@gmail.com \
    --cc=gabe@blackfam.net \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox