Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Veksler <mveksler@techunix.technion.ac.il>
To: Michael Veksler <mveksler@techunix.technion.ac.il>, 	gdb@sourceware.org
Subject: Re: How to call operator<< functions?
Date: Wed, 30 Aug 2006 20:45:00 -0000	[thread overview]
Message-ID: <44F5F8ED.3090300@tx.technion.ac.il> (raw)
In-Reply-To: <20060830202352.GA2018@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Wed, Aug 30, 2006 at 11:05:43PM +0300, Michael Veksler wrote:
>   
> Let's look at one thing at a time.
>
> The first two crashes should, I think, be addressed by this patch. 
> Could you try it?
>   
With the patch it works:

    (gdb) p x.Print(myCout)
    Enter B::Print() this=0xbfffec00
    $1 = void
    (gdb) p ref_x.Print(myCout)
    Enter B::Print() this=0xbfffec00
    $2 = void

Great progress. The most annoying and common failures I have used to be 
seeing is no more.
The other annoying issues sorted by decreasing annoyance :
- this->Print is not always found (I'll try to create a small test-case 
later).
- std::cout related crashes
- print myCout << x --- won't work need to resort to
print 'operator<<........'(myCout, x)

> Some of the later crashes are caused by this:
>
> (gdb) set $a = x.Print
> (gdb) p $a
> $7 = <error reading variable>
>
> I have a whole lot of patches related to member functions, that I
> haven't had time to merge yet - and I would not like to look at this
> until I've done that.
>
>   
This is less critical since this was an attempt to overcome the other bug.


Thanks,

Michael


  reply	other threads:[~2006-08-30 20:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 10:11 Michael Veksler
2006-08-30 11:13 ` Frederic RISS
2006-08-30 13:30   ` Frederic RISS
2006-08-30 13:40     ` Breakpoint Handling in GDB Veenu Verma (AS/EAB)
2006-08-30 13:43       ` Daniel Jacobowitz
2006-08-30 20:30       ` Michael Snyder
2006-08-31 11:34     ` Get versioned minsyms from dynamic symtab (Was: Re: How to call operator<< functions?) Frederic RISS
2006-08-31 12:09       ` Michael Veksler
2006-08-31 12:26         ` Frederic RISS
2006-08-31 13:02           ` Michael Veksler
2006-08-31 13:23             ` Frederic RISS
2006-08-31 16:48               ` Frederic RISS
2006-08-31 16:57                 ` Daniel Jacobowitz
2006-08-31 17:41                   ` Frédéric Riss
2006-08-31 17:45                     ` Daniel Jacobowitz
2006-08-31 19:48                   ` Michael Veksler
2006-08-31 19:52                     ` Daniel Jacobowitz
2006-08-30 12:46 ` How to call operator<< functions? Daniel Jacobowitz
2006-08-30 20:05   ` Michael Veksler
2006-08-30 20:24     ` Daniel Jacobowitz
2006-08-30 20:45       ` Michael Veksler [this message]
2006-08-30 20:54         ` Daniel Jacobowitz
2006-08-31 12:05           ` Michael Veksler

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=44F5F8ED.3090300@tx.technion.ac.il \
    --to=mveksler@techunix.technion.ac.il \
    --cc=gdb@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