Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Alexander Smundak <asmundak@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC][PATCH] Allow JIT unwinder provide symbol information
Date: Fri, 11 Apr 2014 18:58:00 -0000	[thread overview]
Message-ID: <21320.15195.857721.50656@ruffy.mtv.corp.google.com> (raw)
In-Reply-To: <CAHQ51u7ZzfLQp2NH15FzM-pGM+rOyczeAZc2nH-+XS175gTmyw@mail.gmail.com>

Alexander Smundak writes:
 >[...]
 > diff --git a/gdb/jit-reader.in b/gdb/jit-reader.in
 > index 6e2ee64..a6a0ab1 100644
 > --- a/gdb/jit-reader.in
 > +++ b/gdb/jit-reader.in
 > @@ -270,7 +307,14 @@ struct gdb_unwind_callbacks
 >    gdb_unwind_reg_get *reg_get;
 >    gdb_unwind_reg_set *reg_set;
 >    gdb_target_read *target_read;
 > -
 > +  gdb_unwind_stash *stash;
 > +  gdb_unwind_reg_get *cpu_reg_get;
 > +  gdb_find_symbol *find_symbol;
 > +  gdb_get_jtid *get_jtid;
 > +  gdb_enumerate_shared *enumerate_shared;
 > +  gdb_unwind_debug_flag *debug_flag;
 > +  gdb_architecture_name *architecture_name;
 > +  gdb_pointer_size *pointer_size;
 >    /* For internal use by GDB.  */
 >    void *priv_data;
 >  };

Oops, missed this one.

Move the new entries to the end.

@@ -270,7 +307,14 @@ struct gdb_unwind_callbacks
   gdb_unwind_reg_get *reg_get;
   gdb_unwind_reg_set *reg_set;
   gdb_target_read *target_read;

   /* For internal use by GDB.  */
   void *priv_data;
+
+  /* New entries for version 2 interface.  */
+  gdb_unwind_stash *stash;
+  gdb_unwind_reg_get *cpu_reg_get;
+  gdb_find_symbol *find_symbol;
+  gdb_get_jtid *get_jtid;
+  gdb_enumerate_shared *enumerate_shared;
+  gdb_unwind_debug_flag *debug_flag;
+  gdb_architecture_name *architecture_name;
+  gdb_pointer_size *pointer_size;
 };


  parent reply	other threads:[~2014-04-11 18:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26 18:36 Sasha Smundak
2014-01-13 18:25 ` Alexander Smundak
2014-02-07 21:54   ` Alexander Smundak
2014-01-13 18:46 ` Doug Evans
2014-01-15  0:39   ` Alexander Smundak
2014-02-11 22:26     ` Doug Evans
2014-02-12  7:50       ` Doug Evans
2014-02-19  3:30         ` Alexander Smundak
2014-02-19  3:50           ` Eli Zaretskii
2014-02-19  5:23             ` Alexander Smundak
2014-04-11 18:47           ` Doug Evans
2014-04-11 18:58           ` Doug Evans [this message]
2014-04-21  1:35             ` Alexander Smundak
2014-04-21  7:14               ` Eli Zaretskii
2014-04-21 16:43                 ` Alexander Smundak
2014-02-25  1:19         ` Doug Evans
2014-02-25  3:00           ` Alexander Smundak
2014-03-11  1:46           ` Alexander Smundak
2014-02-08  7:08 ` Yao Qi
2014-02-10  2:16   ` Alexander Smundak
2014-02-11 22:00     ` Doug Evans
2014-04-24 13:22 ` Pedro Alves
2014-04-25 23:40   ` Alexander Smundak
2014-04-29 15:22     ` Pedro Alves
2014-05-02 16:58       ` Alexander Smundak
2014-05-19 21:30         ` Alexander Smundak
2014-05-29  1:07       ` Alexander Smundak
2014-06-02  1:15       ` Alexander Smundak

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=21320.15195.857721.50656@ruffy.mtv.corp.google.com \
    --to=dje@google.com \
    --cc=asmundak@google.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