Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Sunil Alankar <sunil.alankar@coware.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 5.2/5.3 breakpoint bug
Date: Wed, 08 Jan 2003 18:24:00 -0000	[thread overview]
Message-ID: <20030108182315.GA27967@nevyn.them.org> (raw)
In-Reply-To: <IMEGIEBLGLIOEGOLAFIEMEOJCEAA.sunil.alankar@coware.com>

I don't have access to Solaris, and I can't see how this would work;
can you send me (privately) a compiled binary that GDB 5.1 can insert
the breakpoint in?

On Wed, Jan 08, 2003 at 10:10:05AM -0800, Sunil Alankar wrote:
> Yes. GDB 5.1 sets break point on func() with the same binary/compiler. 5.2
> and 5.3 also work on Linux but have problems on Solaris.
> 
> --Sunil
> 
> -----Original Message-----
> From: Daniel Jacobowitz [mailto:drow@mvista.com]
> Sent: Wednesday, January 08, 2003 9:31 AM
> To: Sunil Alankar
> Cc: gdb@sources.redhat.com
> Subject: Re: GDB 5.2/5.3 breakpoint bug
> 
> 
> On Sun, Jan 05, 2003 at 03:07:04PM -0800, Sunil Alankar wrote:
> > //-------------------------------------------------------------
> > #include <systemc.h>
> >
> > SC_MODULE(top)
> > {
> >  public:
> >
> >     sc_in_clk iclk;
> >
> >     void func()
> >         {
> >             printf (".");
> >         }
> >
> >     SC_CTOR(top)
> >         {
> >             SC_METHOD(func);
> >             sensitive_pos << iclk;
> >             dont_initialize();
> >         }
> > };
> 
> 
> Func is an inline method.  Does gdb 5.1 really set a breakpoint on it?
> Using the exact same binary and compiler?  I find that pretty
> surprising, since there is no symbol for it anywhere; GDB's support for
> inline methods is pretty lousy right now.
> 
> --
> Daniel Jacobowitz
> MontaVista Software                         Debian GNU/Linux Developer
> 
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-01-08 18:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <IMEGIEBLGLIOEGOLAFIEGELNCEAA.sunil.alankar@coware.com>
2003-01-05 23:10 ` Sunil Alankar
2003-01-05 23:14   ` Sunil Alankar
2003-01-07 23:55     ` Sunil Alankar
2003-01-08  0:52       ` Daniel Jacobowitz
2003-01-08 17:39       ` Daniel Jacobowitz
2003-01-08 18:16         ` Daniel Jacobowitz
2003-01-08 19:22           ` Sunil Alankar
2003-01-08 19:32             ` Daniel Jacobowitz
2003-01-08 19:43               ` Sunil Alankar
2003-01-08 20:42                 ` Sunil Alankar
2003-01-08 20:46                   ` Daniel Jacobowitz
2003-01-08 22:46                     ` Ching Lai
2003-01-09  3:40                       ` Daniel Jacobowitz
2003-01-09  5:18                         ` Ching Lai
2003-01-08 17:30   ` Daniel Jacobowitz
2003-01-08 18:14     ` Sunil Alankar
2003-01-08 18:24       ` Daniel Jacobowitz [this message]
2003-01-29  3:56       ` Daniel Jacobowitz
2003-01-02 20:59 how to access show/set data Kris Warkentin
2003-01-04  2:19 ` GDB 5.2/5.3 breakpoint bug Sunil Alankar
2003-01-04  2:23   ` Daniel Jacobowitz

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=20030108182315.GA27967@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=sunil.alankar@coware.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