public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: <Paul_Koning@Dell.com>
To: <daniel.gutson@tallertechnologies.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: break on C++ global objects ctors
Date: Mon, 31 Mar 2014 14:16:00 -0000	[thread overview]
Message-ID: <C75A84166056C94F84D238A44AF9F6AD16C9B531@AUSX10MPC103.AMER.DELL.COM> (raw)
In-Reply-To: <CAF5HaEW8iNZHEx+SA=MBu26XMZO+ENwqXhoJwLtZSMCHc_jNcA@mail.gmail.com>


On Mar 31, 2014, at 10:10 AM, Daniel Gutson <daniel.gutson@tallertechnologies.com> wrote:

> On Mon, Mar 31, 2014 at 10:56 AM,  <Paul_Koning@dell.com> wrote:
>> This certainly should be easily doable, just in gdb.  FWIW, if you start a program with gdbserver and then connect to it from gdb ("target remote" to gdbserver), the program is stopped at the first instruction, way before "main".
> 
> That doesn't solve how gdb detects the beginning of each ctor function.

I don’t know what problem you’re referring to.  A constructor is just a function, which has a name, and you can set a breakpoint on it.  

If for some reason that’s not working, that would be a bug, but I’ve used breakpoints on constructors for a long time and it seems to work when I try it.

	paul

  reply	other threads:[~2014-03-31 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 18:22 Daniel Gutson
2014-03-31 12:24 ` Daniel Gutson
2014-03-31 13:56   ` Paul_Koning
2014-03-31 14:10     ` Daniel Gutson
2014-03-31 14:16       ` Paul_Koning [this message]
2014-03-31 14:41         ` Daniel Gutson
2014-09-26 18:00           ` Daniel Gutson

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=C75A84166056C94F84D238A44AF9F6AD16C9B531@AUSX10MPC103.AMER.DELL.COM \
    --to=paul_koning@dell.com \
    --cc=daniel.gutson@tallertechnologies.com \
    --cc=gdb-patches@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).