Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Koon-Seng Lim <koonseng@ctr.columbia.edu>
To: 'Daniel Jacobowitz' <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: RE: Setting breakpoints in a virtual function on a dynamically loaded DLL
Date: Sun, 31 Mar 2002 18:22:00 -0000	[thread overview]
Message-ID: <000001c1d923$e00fa910$9e01a8c0@rogue> (raw)
In-Reply-To: <20020331200737.A22942@nevyn.them.org>



> -----Original Message-----
> From: Daniel Jacobowitz [mailto:drow@mvista.com]
> Sent: Sunday, March 31, 2002 8:08 PM
> To: Koon-Seng Lim
> Cc: gdb@sources.redhat.com
> Subject: Re: Setting breakpoints in a virtual function on a
dynamically
> loaded DLL
> 
> On Sun, Mar 31, 2002 at 07:52:31PM -0500, Koon-Seng Lim wrote:
> > Hi,
> >
> > I'm trying to set a breakpoint in a virtual function
(new_foo::bar())
> > implemented in a DLL (testdll.dll) which I load dynamically from an
.exe
> > (fooloader.exe). I get the following errors:
> >
> > $ gdb fooloader.exe
> > ...
> > (gdb) shared testdll.dll
> > (gdb)
> > (gdb) break new_foo::bar
> > Error: Cannot access memory at address 0x010001014
> >
> > If I forcibly set a breakpoint at new_foo::bar using the GUI, I get
an
> > error dialog that says "cannot insert breakpoint 1:" and the message
> > "Error: Cannot access memory at address 0x01000101e" in the console
> > window.
> >
> > My question is:
> > 1. Is there any way at all to set a breakpoint in the testdll.dll?
> > 2. Did I doing something silly? The code is very simple and it steps
> > correctly under the MSVC debugger.
> >
> > I'm running gdb 5.0 with the Insight GUI on cygwin 1.3.10 on a
windows
> > box. Any help is greatly appreciated!!!
> 
> - What version of GCC are you using?
> - Please try a GDB snapshot; 5.0 is very old now, and has rotten C++
> support.
> 
> --
> Daniel Jacobowitz                           Carnegie Mellon University
> MontaVista Software                         Debian GNU/Linux Developer

Thanks for the reply!

I'm using gcc version 2.95.3-5. I've just tried out the latest weekly
snapshot(insight+dejagnu-weekly-20020326.tar.bz2) but alas, he problem
remains.

Thanks

-Koon Seng


      reply	other threads:[~2002-04-01  2:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-31 16:53 Koon-Seng Lim
2002-03-31 17:07 ` Daniel Jacobowitz
2002-03-31 18:22   ` Koon-Seng Lim [this message]

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='000001c1d923$e00fa910$9e01a8c0@rogue' \
    --to=koonseng@ctr.columbia.edu \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.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