Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Andrew Haley <aph@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Java Inferior Call Take 2
Date: Thu, 24 Jun 2004 17:57:00 -0000	[thread overview]
Message-ID: <873c4kq29c.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20040623230138.GA6426@nevyn.them.org>

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

Daniel> In C++, the debug information marks whether a constructor was written
Daniel> by the user (i.e. the type really contains a constructor) or by the
Daniel> compiler (i.e. implicit).  I imagine Java's debug information has the
Daniel> same thing.

The information is there, though I don't know whether gcj puts it
into the .o.

Daniel> (This shouldn't affect breakpointing it for users who know the
Daniel> constructor exists.)

It is also actually useful on occasion to put a breakpoint on <clinit>.
This can let you see when your class is initialized, and it will let
you step through the static blocks and static field initializers.

Tom


  reply	other threads:[~2004-06-24 17:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 20:53 Jeff Johnston
2004-06-11 17:49 ` Jeff Johnston
2004-06-17  3:06 ` Daniel Jacobowitz
2004-06-17 20:52   ` Jeff Johnston
2004-06-19 23:59     ` Daniel Jacobowitz
2004-06-21 10:49       ` Andrew Haley
2004-06-21 15:17       ` Andrew Haley
2004-06-23 11:06         ` Andrew Haley
2004-06-23 13:47           ` Daniel Jacobowitz
2004-06-23 16:06             ` Andrew Haley
2004-06-23 16:08               ` Daniel Jacobowitz
2004-06-23 21:55             ` Jeff Johnston
2004-06-23 23:01               ` Daniel Jacobowitz
2004-06-24 17:57                 ` Tom Tromey [this message]
2004-07-06 21:47                 ` Jeff Johnston
2004-07-26 19:49                   ` Jeff Johnston
2004-07-26 19:51                     ` Daniel Jacobowitz
2004-08-02 10:17                       ` Andrew Haley
2004-08-02 15:17                         ` Andrew Haley
2004-08-02 20:20                           ` Daniel Jacobowitz
2004-08-03 18:45                             ` Andrew Haley
2004-08-16 13:08                               ` Andrew Haley
2004-08-16 13:18                                 ` Daniel Jacobowitz
2004-08-16 20:32                                   ` Daniel Jacobowitz
2004-08-16 20:35                   ` Daniel Jacobowitz
2004-08-24 18:53                     ` [RFA]: Java Inferior Call Take 3 Jeff Johnston
2004-08-24 19:05                       ` Michael Chastain
2004-08-24 19:28                         ` Jeff Johnston
2004-08-24 19:10                       ` Michael Chastain
2004-08-24 19:48                         ` Andrew Cagney
2004-09-01  4:51                       ` Jim Blandy
2004-09-09 23:41                         ` Jeff Johnston
2004-09-10 20:12                           ` Jim Blandy
2004-09-15 22:58                             ` Jeff Johnston
2004-09-20 18:23                               ` Jim Blandy
2004-09-20 20:19                                 ` Jeff Johnston

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=873c4kq29c.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=aph@redhat.com \
    --cc=drow@false.org \
    --cc=gdb-patches@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