public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Smith <paul@mad-scientist.net>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Help using the GDB C++ STL pretty-printers / xmethods
Date: Sun, 08 May 2022 15:44:36 -0400	[thread overview]
Message-ID: <7c6d308fdbbcabf83dd5423c33ca851666beaae7.camel@mad-scientist.net> (raw)
In-Reply-To: <CAH6eHdRvg8FrW9ZSQ9ytd16-VbjDtuzSj8v6gokn59icjp33Lw@mail.gmail.com>

On Sun, 2022-05-08 at 09:16 +0100, Jonathan Wakely wrote:
> > gdb.set_convenience_variable('mgr', val['mgr'])
> > init = gdb.parse_and_eval('$mgr->initialized')
> > 
> > This will use the xmethod to evaluate the expression.
> 
> And then:
> 
> if init:
>     return gdb.parse_and_eval('*$mgr')

Unfortunately, this doesn't work :(.  I can't do it from the GDB
command line or python (I have tried both with the same results). 
Something about convenience variables doesn't play well with xmethods 
(or maybe this xmethod implementation specifically?)

Very simple test program:

  /* /tmp/sleep.cpp */
  #include <unistd.h>
  #include <memory>

  class Foo { public: int val = 0; };

  std::unique_ptr<Foo> foo;

  int main()
  {
      foo = std::make_unique<Foo>();
      sleep(100000);
      return 0;
  }

Compile it & run it:

  g++ -ggdb3 -o /tmp/sleep /tmp/sleep.cpp
  /tmp/sleep &

Now attach with GDB (probably you can just run it in GDB but I did it
like this so I could detach/reattach):

  gdb -p <pid>

Switch to main, set an convenience variable to "foo", then try to use
xmethods on it and no joy:

  (gdb) fr 3
  11          sleep(100000);

  (gdb) p foo
  $1 = std::unique_ptr<Foo> = {
    get() = 0x105aeb0
  }
  (gdb) p foo->val
  $2 = 0

  (gdb) set $xx = foo
  (gdb) p $xx
  $3 = std::unique_ptr<Foo> = {
    get() = 0x105aeb0
  }

  (gdb) p $xx->val
  Attempt to take address of value not located in memory.

Same behavior with GDB 10.2 and 12.1.

  parent reply	other threads:[~2022-05-08 19:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07  1:23 Paul Smith
2022-05-07 11:19 ` Hannes Domani
2022-05-07 15:07   ` Paul Smith
2022-05-07 15:35     ` Jonathan Wakely
2022-05-07 19:07       ` Paul Smith
2022-05-07 19:51         ` Jonathan Wakely
2022-05-07 23:08           ` Paul Smith
2022-05-08  8:13             ` Jonathan Wakely
2022-05-08  8:16               ` Jonathan Wakely
2022-05-08 14:09                 ` Paul Smith
2022-05-08 14:36                   ` Jonathan Wakely
2022-05-08 19:44                 ` Paul Smith [this message]
2022-05-08 20:26                   ` Paul Smith
2022-05-09 10:47                     ` Hannes Domani
2022-05-09 10:52                       ` Hannes Domani
2022-05-09  9:32                   ` Jonathan Wakely
2022-05-09 11:23                     ` Jonathan Wakely
2022-05-09 14:05                       ` Paul Smith
2022-05-09 14:40                         ` Paul Smith
2022-05-07 15:44     ` Hannes Domani
2022-05-07 15:25 ` Jonathan Wakely

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=7c6d308fdbbcabf83dd5423c33ca851666beaae7.camel@mad-scientist.net \
    --to=paul@mad-scientist.net \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).