Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch v7 05/24] frame: artificial frame id's
Date: Wed, 11 Dec 2013 19:58:00 -0000	[thread overview]
Message-ID: <20131211195847.GC22687@host2.jankratochvil.net> (raw)
In-Reply-To: <1385735899-12481-6-git-send-email-markus.t.metzger@intel.com>

On Fri, 29 Nov 2013 15:38:00 +0100, Markus Metzger wrote:
> --- a/gdb/frame.c
> +++ b/gdb/frame.c
> @@ -504,6 +504,19 @@ frame_id_build_wild (CORE_ADDR stack_addr)
>    return id;
>  }
>  

/* See frame.h.  */

> +struct frame_id
> +frame_id_build_artificial (CORE_ADDR code_addr,
> +			   CORE_ADDR special_addr)
> +{
> +  struct frame_id id = null_frame_id;
> +
> +  id.code_addr = code_addr;
> +  id.code_addr_p = 1;
> +  id.special_addr = special_addr;
> +  id.special_addr_p = 1;
> +  return id;
> +}
> +
>  int
>  frame_id_p (struct frame_id l)
>  {
[...]
> --- a/gdb/frame.h
> +++ b/gdb/frame.h
> @@ -174,6 +174,12 @@ extern struct frame_id frame_id_build_special (CORE_ADDR stack_addr,
>     as the special identifier address are set to indicate wild cards.  */
>  extern struct frame_id frame_id_build_wild (CORE_ADDR stack_addr);
>  
> +/* Construct an artificial frame ID.  The first parameter is the frame's
> +   constant code address (typically the entry point), and the second the

                                  the function entry point

> +   frame's special identifier address.  */
> +extern struct frame_id frame_id_build_artificial (CORE_ADDR code_addr,
> +						  CORE_ADDR special_addr);
> +
>  /* Returns non-zero when L is a valid frame (a valid frame has a
>     non-zero .base).  The outermost frame is valid even without an
>     ID.  */
> -- 
> 1.8.3.1


Thanks,
Jan


  parent reply	other threads:[~2013-12-11 19:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 14:38 [patch v7 00/24] record-btrace: reverse Markus Metzger
2013-11-29 14:38 ` [patch v7 14/24] record-btrace: supply register target methods Markus Metzger
2013-11-29 14:38 ` [patch v7 08/24] record-btrace: start counting at one Markus Metzger
2013-11-29 14:38 ` [patch v7 04/24] frame: add frame_is_tailcall function Markus Metzger
2013-11-29 14:38 ` [patch v7 03/24] gdbarch: add instruction predicate methods Markus Metzger
2013-12-11 12:16   ` Pedro Alves
2013-11-29 14:38 ` [patch v7 01/24] btrace, linux: fix memory leak when reading branch trace Markus Metzger
2013-11-29 14:39 ` [patch v7 13/24] target: add ops parameter to to_prepare_to_store method Markus Metzger
2013-11-29 14:39 ` [patch v7 18/24] record-btrace: add to_wait and to_resume target methods Markus Metzger
2013-11-29 14:39 ` [patch v7 09/24] btrace: increase buffer size Markus Metzger
2013-11-29 14:39 ` [patch v7 16/24] record-btrace, frame: supply target-specific unwinder Markus Metzger
2013-11-29 14:39 ` [patch v7 17/24] record-btrace: provide xfer_partial target method Markus Metzger
2013-11-29 14:39 ` [patch v7 19/24] record-btrace: provide target_find_new_threads method Markus Metzger
2013-11-29 14:39 ` [patch v7 23/24] record-btrace: show trace from enable location Markus Metzger
2013-11-29 14:39 ` [patch v7 05/24] frame: artificial frame id's Markus Metzger
2013-12-11 12:24   ` Pedro Alves
2013-12-11 19:58   ` Jan Kratochvil [this message]
2013-11-29 14:39 ` [patch v7 11/24] record-btrace: make ranges include begin and end Markus Metzger
2013-11-29 14:39 ` [patch v7 07/24] record-btrace: fix insn range in function call history Markus Metzger
2013-11-29 14:39 ` [patch v7 12/24] btrace: add replay position to btrace thread info Markus Metzger
2013-11-29 14:40 ` [patch v7 21/24] record-btrace: extend unwinder Markus Metzger
2013-12-11 19:57   ` Jan Kratochvil
2013-11-29 14:40 ` [patch v7 06/24] btrace: change branch trace data structure Markus Metzger
2013-11-29 14:40 ` [patch v7 15/24] frame, backtrace: allow targets to supply a frame unwinder Markus Metzger
2013-11-29 14:41 ` [patch v7 20/24] record-btrace: add record goto target methods Markus Metzger
2013-11-29 14:41 ` [patch v7 02/24] btrace: uppercase btrace_read_type Markus Metzger
2013-12-11 12:11   ` Pedro Alves
2013-11-29 14:42 ` [patch v7 10/24] record-btrace: optionally indent function call history Markus Metzger
2013-11-29 15:05 ` [patch v7 22/24] btrace, gdbserver: read branch trace incrementally Markus Metzger
2013-12-11 19:58   ` Jan Kratochvil
2013-12-12  8:24     ` Metzger, Markus T
2013-12-12  9:13       ` Jan Kratochvil
2013-11-29 15:11 ` [patch v7 24/24] record-btrace: add (reverse-)stepping support Markus Metzger

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=20131211195847.GC22687@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.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