public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'personel personel'" <lepascal01@yahoo.com>, 	<gdb@sourceware.org>
Subject: RE: Debugging a Vlc dll with GDB.
Date: Thu, 06 Dec 2007 17:53:00 -0000	[thread overview]
Message-ID: <057001c83830$f06314b0$2e08a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <422087.46834.qm@web57709.mail.re3.yahoo.com>

On 06 December 2007 17:38, personel personel wrote:

> Hello,
> 
> 
> I am currently using GDB v.6.5.50.20060706. One of my
> colleague built an application (VLCTest.exe) by using
> Visual Studio C++ 6.0 

> It tried to put a breakpoint into VLCTest.exe but it
> did not work:
> 
> gdb -silent -e VLCTest.exe -s VLCTest.exe == "no
> debugging symbols found"

> Can you suggest me a method?


  GDB (and binutils in general) doesn't speak the language used by MSVC's
debugging info (CodeView format; binutils uses STABS on windows).  Off the top
of my head, your options are:

1.  Use mingw+gcc to compile instead of MSVC, so that you get debug info
suitable for gdb.
2.  Use Microsoft's debugger that's built into MSVC, or their standalone
debugger "WinDbg".
3.  Use gdb, and deal with the lack of symbols by using "dumpbin /symbols" to
get a list of all the symbols and keep it handy in notepad while you're using
gdb, looking up the address that corresponds to a symbol whenever you want to
set a breakpoint and entering it into gdb in hex.



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2007-12-06 17:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 17:38 personel personel
2007-12-06 17:53 ` Dave Korn [this message]
2007-12-06 18:23 ` Daniel Jacobowitz
2007-12-06 20:15   ` personel personel
2007-12-06 20:29     ` Daniel Jacobowitz
2007-12-06 20:57       ` Brian Dessent
2007-12-07  0:28         ` Pedro Alves
2007-12-07  0:42           ` Daniel Jacobowitz
2007-12-07  1:57             ` Pedro Alves
2007-12-07 13:54               ` Daniel Jacobowitz
2007-12-08 10:54                 ` Eli Zaretskii
2007-12-07 16:21             ` Dave Korn

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='057001c83830$f06314b0$2e08a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=gdb@sourceware.org \
    --cc=lepascal01@yahoo.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).