public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: Daniel Jacobowitz <drow@false.org>
Cc: personel personel <lepascal01@yahoo.com>, gdb@sourceware.org
Subject: Re: Debugging a Vlc dll with GDB.
Date: Thu, 06 Dec 2007 20:57:00 -0000	[thread overview]
Message-ID: <47586224.CE80C330@dessent.net> (raw)
In-Reply-To: <20071206202850.GA27429@caradoc.them.org>

Daniel Jacobowitz wrote:

> >    (gdb) break libvlc_new
> >     No symbol table is loaded. use the file command
> 
> Try "set pending on"?  Or you may need a newer version of GDB.

I don't think pending being off is the problem, but you do need a more
recent gdb than what ships with Cygwin.  With recent CVS gdb I have had
success with something like:

gdb VLCTest.exe
add-shared-symbol-files libvlc.dll
b libvlc_new
run

I have always found debugging stripped binaries on Win32 with gdb to be
somewhat unpleasant.  After the first time that the program has run and
terminates, all the pending breakpoint stuff usually seems to work fine,
it's just that initially when nothing has loaded yet it does not.  So
that's another workaround, just run the inferior to completion without
any breakpoints and then start debugging the second run.

Brian

  reply	other threads:[~2007-12-06 20:57 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
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 [this message]
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=47586224.CE80C330@dessent.net \
    --to=brian@dessent.net \
    --cc=drow@false.org \
    --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).