public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: personel personel <lepascal01@yahoo.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: Debugging a Vlc dll with GDB.
Date: Thu, 06 Dec 2007 20:15:00 -0000	[thread overview]
Message-ID: <433908.24398.qm@web57701.mail.re3.yahoo.com> (raw)
In-Reply-To: <20071206182343.GA16137@caradoc.them.org>

Hello Daniel,


I tried:

    gdb -silent -e VLCTest.exe -s VLCTest.exe == "no
                     debugging symbols found"

   (gdb) break libvlc_new
    No symbol table is loaded. use the file command 


As you can see, gdb does not ask me if I want to set a
pending breakpoint. Why? It cant read any symbol table
so how can it knows that the function is not into
VLCTest.exe but in a DLL?

If you have another suggestion, I would be pleased.

Thank you,

abraxis


--- Daniel Jacobowitz <drow@false.org> wrote:

> On Thu, Dec 06, 2007 at 09:38:10AM -0800, personel
> personel wrote:
> > 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 and used the MFC.
> 
> As Dave mentioned, we can not do source level
> debugging of MSVC++
> compiled applications.
> 
> > Instead of it I can put a breakpoint into
> libvlc.dll
> > (let's say function libvlc_new()). I tried but it
> did
> > not work:
> >  
> > gdb -silent -e VLCTest.exe -s VLCTest.exe == "no
> > debugging symbols found"
> > file libvlc.dll          == reading symbols from
> > libvlc.dll ... done 
> > break libvlc_new   == breakpoint 1 at bla bla bla
> > run VLCTest.exe  == error creating process
> > /cygdrive/c/cygwin/myapp/libvlc.dll
> 
> Skip the "file" command.  Say yes when GDB asks if
> the breakpoint
> should be created pending.
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery
> 



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 

  reply	other threads:[~2007-12-06 20:15 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 [this message]
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=433908.24398.qm@web57701.mail.re3.yahoo.com \
    --to=lepascal01@yahoo.com \
    --cc=drow@false.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).