Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix another stale frame_info *
Date: Fri, 24 Feb 2012 15:41:00 -0000	[thread overview]
Message-ID: <20120224153702.GA20145@host2.jankratochvil.net> (raw)
In-Reply-To: <4F47AC84.9080807@redhat.com>

On Fri, 24 Feb 2012 16:28:04 +0100, Pedro Alves wrote:
> Yeah.  If we swap the order we do things, we can avoid needing this
> bit.  WDYT?  It seems slightly cleaner to me.  Tested on x86_64 Fedora 16.

In general yes just this patch is not there yet.


> --- a/gdb/breakpoint.c
> +++ b/gdb/breakpoint.c
[...]
>    if (frame_id_p (frame_unwind_caller_id (frame)))
>      {
> -      sal = find_pc_line (frame_unwind_caller_pc (frame), 0);
> -      sal.pc = frame_unwind_caller_pc (frame);
> +      struct symtab_and_line sal2;
> +
> +      sal2 = find_pc_line (frame_unwind_caller_pc (frame), 0);
> +      sal2.pc = frame_unwind_caller_pc (frame);
>        breakpoint2 = set_momentary_breakpoint (frame_unwind_caller_arch (frame),
> -					      sal,
> +					      sal2,
>  					      frame_unwind_caller_id (frame),
>  					      bp_until);
>        make_cleanup_delete_breakpoint (breakpoint2);

Here is still in the code:
      set_longjmp_breakpoint (tp, frame_unwind_caller_id (frame));



Thanks,
Jan


  reply	other threads:[~2012-02-24 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  8:38 Jan Kratochvil
2012-02-24 15:37 ` Pedro Alves
2012-02-24 15:41   ` Jan Kratochvil [this message]
2012-02-24 15:54     ` Pedro Alves
2012-02-24 16:05       ` Jan Kratochvil
2012-02-24 16:32         ` Pedro Alves

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=20120224153702.GA20145@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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