public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: personel personel <lepascal01@yahoo.com>
To: gdb@sourceware.org
Subject: Debugging a Vlc dll with GDB.
Date: Thu, 06 Dec 2007 17:38:00 -0000	[thread overview]
Message-ID: <422087.46834.qm@web57709.mail.re3.yahoo.com> (raw)

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 and used the MFC. His
application uses the libvlc.dll of an open source
application called Vlc. Unfortunately, Vlc has some
bug(s) and we want to find them, correct them and
suggest patches to the maintainers. So, our work will
help the open source community.
 
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"
 
 
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
 
 
As you can see my goal is to step into the libvlc.dll.
Can you suggest me a method?
I tought about creating a new project under Eclipse to
build VLCTest.exe but it seems
to be an overkill.
 
 
Best regards,
 
abraxis



      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 17:38 personel personel [this message]
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
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=422087.46834.qm@web57709.mail.re3.yahoo.com \
    --to=lepascal01@yahoo.com \
    --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).