Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Dave Korn" <dk@artimi.com>
To: "'Caolan McNamara'" <caolan@csn.ul.ie>, <gdb@sources.redhat.com>
Subject: RE: OpenOffice.org and gdb
Date: Tue, 20 Jul 2004 19:41:00 -0000	[thread overview]
Message-ID: <NUTMEGLMOEYzk8TRAzT00000962@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <20040720102727.GA15676@skynet.ie>

> -----Original Message-----
> From: gdb-owner On Behalf Of Caolan McNamara
> Sent: 20 July 2004 11:27

> 2. make gdbtestc++
> 
> The known issues of gdb/1091 & gdb/1193. Not being able to set
> breakpoints in constructors :-(

> I can work around 4 for my own needs by building the bit of OOo that
> contains main with debugging enabled, and I can work around 3 by
> restricting myself to line numbers, but 1 and 2 are a real curse.
> 
> Are there any other known workarounds that I can employ, or is there
> simply a better compile flag incantation I should use :-) I guess
> I should just log bugs against them.

  For issue 2, see this thread from earlier this week:

http://sources.redhat.com/ml/gdb/2004-07/msg00161.html
Subject: "How to setup a breakpoint on constructor"

  In the archives, the thread is broken (someone's mailer doesn't handle the
references header properly I guess); you'll need to look at the index at

http://sources.redhat.com/ml/gdb/2004-07/

for all the posts with the same subject, and in particular you might want to
have a go with the patch from 

http://sources.redhat.com/ml/gdb/2004-07/msg00163.html


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


      reply	other threads:[~2004-07-20 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 10:35 Caolan McNamara
2004-07-20 19:41 ` Dave Korn [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=NUTMEGLMOEYzk8TRAzT00000962@NUTMEG.CAM.ARTIMI.COM \
    --to=dk@artimi.com \
    --cc=caolan@csn.ul.ie \
    --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