From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] handle an unspecified return address column
Date: Tue, 26 Nov 2013 14:41:00 -0000 [thread overview]
Message-ID: <201311261430.rAQEUFIu001724@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20131126135519.GI3114@adacore.com> (message from Joel Brobecker on Tue, 26 Nov 2013 17:55:19 +0400)
> Date: Tue, 26 Nov 2013 17:55:19 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> > > gdb/ChangeLog:
> > >
> > > PR backtrace/16155:
> > > * dwarf2-frame.c (dwarf2_frame_cache): Remove condition that
> > > sets cache->undefined_retaddr to 1 if there is no column in
> > > the frame info for the return register.
> > >
> > > Tested on x86_64-linux, no regression. It also fixes all regressions
> > > observed on arm-elf and ppc-elf.
> > >
> > > Can you tell me what you think?
> >
> > Please start with backing out the original change.
>
> I would gladly do so, but can you explain the rationale behind your
> request? Is it to facilitate review of this patch? Or is it because
> you think all of the original patch needs to go? I felt that the patch
> just overachieved a bit from what it initially set out to do (detect
> unspecified return registers), and so I felt it was ok to send a
> followup rather than redo it entirely.
Pretty much both. The original diff was clearly wrong, and it is best
to have the history reflect that clearly. But it will also make the
review easier. To be honest, I think the conditional, after your
modification, is too confusing.
Didn't realize that the tests were part of the same commit though. So
you probably can't simply use git revert. Perhaps that means we
should commit testsuite changes seperately in the future.
next prev parent reply other threads:[~2013-11-26 14:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 20:51 [PATCH 0/2] fix multi-threaded unwinding on AArch64 Tom Tromey
2013-11-13 20:51 ` [PATCH 2/2] handle an unspecified return address column Tom Tromey
2013-11-22 18:22 ` Tom Tromey
2013-11-26 13:55 ` Joel Brobecker
2013-11-26 14:30 ` Mark Kettenis
2013-11-26 14:37 ` Joel Brobecker
2013-11-26 14:41 ` Mark Kettenis [this message]
2013-11-26 14:42 ` Joel Brobecker
2013-11-26 14:50 ` Tom Tromey
2013-11-26 15:05 ` Tom Tromey
2013-11-26 15:16 ` Tom Tromey
2013-11-26 16:11 ` Joel Brobecker
2013-11-13 22:03 ` [PATCH 1/2] avoid infinite loop with bad debuginfo Tom Tromey
2013-11-14 17:34 ` Pedro Alves
2013-11-18 18:25 ` Tom Tromey
2013-11-19 15:10 ` Pedro Alves
2013-11-19 15:47 ` Tom Tromey
2013-11-19 16:33 ` Pedro Alves
2013-11-19 19:07 ` Tom Tromey
2013-11-19 20:24 ` Pedro Alves
2013-11-19 20:56 ` Tom Tromey
2013-11-20 18:27 ` [PATCH] Don't let two frames with the same id end up in the frame chain. (Re: [PATCH 1/2] avoid infinite loop with bad debuginfo) Pedro Alves
2013-11-21 0:33 ` Tom Tromey
2013-11-21 16:40 ` Pedro Alves
2013-11-21 19:25 ` Tom Tromey
2013-11-22 14:13 ` [COMMITTED] Make use of the frame stash to detect wider stack cycles. (was: Re: [PATCH] Don't let two frames with the same id end up in the frame chain. (Re: [PATCH 1/2] avoid infinite loop with bad debuginfo)) Pedro Alves
2013-11-22 14:29 ` [PATCH] Don't let two frames with the same id end up in the frame chain. (Re: [PATCH 1/2] avoid infinite loop with bad debuginfo) Pedro Alves
2013-11-22 14:52 ` [PATCH 1/2] avoid infinite loop with bad debuginfo Pedro Alves
2013-11-22 17:16 ` Tom Tromey
2013-11-22 17:56 ` Pedro Alves
2013-11-19 15:52 ` Tom Tromey
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=201311261430.rAQEUFIu001724@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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