Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix stepping bug associated with non-contiguous blocks
Date: Mon, 15 Jul 2019 15:21:00 -0000	[thread overview]
Message-ID: <87ef2r9vd5.fsf@tromey.com> (raw)
In-Reply-To: <20190714000108.15420-1-kevinb@redhat.com> (Kevin Buettner's	message of "Sat, 13 Jul 2019 17:01:08 -0700")

>>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:

Kevin> gdb/ChangeLog:

Kevin> 	* infrun.c (fill_in_stop_func): Use find_pc_partial_function
Kevin> 	instead of find_function_entry_range_from_pc.

Thanks for the explanation.  I think this makes sense.

Kevin> +	  ecs->stop_func_start
Kevin> +	    += gdbarch_deprecated_function_start_offset (gdbarch);

This hook is only used by VAX.  I wonder if we could delete it somehow.

Tom


  reply	other threads:[~2019-07-15 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14  0:01 Kevin Buettner
2019-07-15 15:21 ` Tom Tromey [this message]
2019-07-15 21:11   ` Kevin Buettner
2019-07-15 21:53     ` Kevin Buettner
2019-07-18 13:36       ` Tom Tromey
2019-07-27 20:49 ` Kevin Buettner

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=87ef2r9vd5.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@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