Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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:30:00 -0000	[thread overview]
Message-ID: <201311261348.rAQDmBs1032481@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20131126133446.GA28596@adacore.com> (message from Joel Brobecker	on Tue, 26 Nov 2013 17:34:46 +0400)

> Date: Tue, 26 Nov 2013 17:34:46 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> 
> Hi Tom,
> 
> On Wed, Nov 13, 2013 at 01:51:13PM -0700, Tom Tromey wrote:
> > Debugging PR 16155 further, I found that the DWARF unwinder found the
> > function in question, but thought it had no registers saved
> > (fs->regs.num_regs == 0).
> > 
> > It seems to me that if a frame does not specify the return address
> > column, or if the return address column is explicitly marked as
> > DWARF2_FRAME_REG_UNSPECIFIED, then we should set the
> > "undefined_retaddr" flag and let the DWARF unwinder gracefully stop.
> > 
> > This patch implements that idea.
> > 
> > With this patch the backtrace works properly:
> > 
> >     (gdb) bt
> >     #0  0x0000007fb7ed485c in nanosleep () from /lib64/libc.so.6
> >     #1  0x0000007fb7ed4508 in sleep () from /lib64/libc.so.6
> >     #2  0x00000000004008bc in thread_function (arg=0x4) at threadapply.c:73
> >     #3  0x0000007fb7fad950 in start_thread () from /lib64/libpthread.so.0
> >     #4  0x0000007fb7f0956c in clone () from /lib64/libc.so.6
> > 
> > 2013-11-13  Tom Tromey  <tromey@redhat.com>
> > 
> > 	PR backtrace/16155:
> > 	* dwarf2-frame.c (dwarf2_frame_cache): Set undefined_retaddr if
> > 	the return address column is unspecified.
> 
> I just found out that this patch causes some problems on at least
> arm-elf and ppc-elf. Attached is a proposed patch, with associated
> analysis.
> 
> 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.


  reply	other threads:[~2013-11-26 13:48 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 [this message]
2013-11-26 14:37       ` Joel Brobecker
2013-11-26 14:41         ` Mark Kettenis
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=201311261348.rAQDmBs1032481@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