From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Joel Brobecker <brobecker@gnat.com>, Jim Blandy <jimb@redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] parse and eval breakpoint conditions with correct language
Date: Thu, 11 Sep 2003 19:54:00 -0000 [thread overview]
Message-ID: <20030911195423.GA21025@nevyn.them.org> (raw)
In-Reply-To: <3F60CB0C.5060504@redhat.com>
On Thu, Sep 11, 2003 at 03:20:44PM -0400, Andrew Cagney wrote:
>
> >Groumf! Our nightly regression test showed a small regression
> >which does not appear on my machine. We have an all-Ada program which
> >defines a function named Func1, and here is what the test does:
> >
> > (gdb) break *Func1'Address
> > (gdb) run
>
> I've been wondering if this language stuff was going to interact badly
> with breakpoints. Anyway, is it possible to create an equivalent gcj
> test case since gcj is likely more accessable to developers?
I think this is going to become an increasingly prominent problem.
You can create testcases for this in C++, if your system starts C++
programs up in startup code which is auto(asm) instead of c++. I think
it's as simple as:
(gdb) break classname::func
And we won't correctly load the class. This happens on Solaris, not
sure about GNU/Linux.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-09-11 19:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 1:54 Joel Brobecker
2003-09-10 17:31 ` Jim Blandy
2003-09-11 18:09 ` Joel Brobecker
2003-09-11 18:42 ` Paul Koning
2003-09-11 19:30 ` Joel Brobecker
2003-09-12 1:33 ` Andrew Cagney
2003-09-12 5:46 ` Joel Brobecker
2003-09-15 3:09 ` Jim Blandy
2003-09-15 19:00 ` Joel Brobecker
2003-09-11 19:20 ` Andrew Cagney
2003-09-11 19:32 ` Joel Brobecker
2003-09-11 19:54 ` Daniel Jacobowitz [this message]
2003-09-11 22:20 ` Jim Blandy
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=20030911195423.GA21025@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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