Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: graceful unwind termination when we'd need unavailable/uncollect memory or registers to unwind further
Date: Mon, 28 Feb 2011 15:56:00 -0000	[thread overview]
Message-ID: <201102281555.56478.pedro@codesourcery.com> (raw)
In-Reply-To: <20110228154132.GA7881@host1.dyn.jankratochvil.net>

On Monday 28 February 2011 15:41:32, Jan Kratochvil wrote:
> In my case:
> 
> (gdb) tfind 0
> Found trace frame 0, tracepoint 2
> #0  f () at 1.c:11
> 11          v++;
> (gdb) bt
> #0  f () at 1.c:11
> Backtrace stopped: Not enough registers or memory available to unwind further
> (gdb) 
> 
> That is without that <unavailable>.  I think it is a bug.

That's expected.  In my example, the _PC_ was not
unwoundable in the outermost unwindable frame, but other
registers were.  In your example, it was, and I'm going
to guess that since you haven't collected any registers,
you're seeing the dwarf unwinder not being able to compute
the CFA.

In my example, notice info registers in the outermost
frame:

(gdb) bt
#0  begin () at ../../../src/gdb/testsuite/gdb.trace/unavailable.cc:180
#1  0x0000000000400b69 in main (argc=1, argv=0x7fffa180ace8, envp=0x7fffa180acf8) at ../../../src/gdb/testsuite/gdb.trace/unavailable.cc:329
#2  <unavailable> in ?? ()
Backtrace stopped: Not enough registers or memory available to unwind further
(gdb) up
#1  0x0000000000400b69 in main (argc=1, argv=0x7fffa180ace8, envp=0x7fffa180acf8) at ../../../src/gdb/testsuite/gdb.trace/unavailable.cc:329
329       begin ();
(gdb) 
#2  <unavailable> in ?? ()
(gdb) info registers 
rax            0x7fa45460eec8   140343767002824
rbx            0x0      0
rcx            0x5      5
rdx            0x7fffa180acf8   140735902952696
rsi            0x7fffa180ace8   140735902952680
rdi            0x1      1
rbp            *value not available*
rsp            0x7fffa180ac10   0x7fffa180ac10
r8             0x7fa45460d300   140343766995712
r9             0x7fa454dc05c0   140343775069632
r10            0x7fffa180a8f0   140735902951664
r11            0x7fa4542c8770   140343763568496
r12            0x4006b0 4196016
r13            0x7fffa180ace0   140735902952672
r14            0x0      0
r15            0x0      0
rip            *value not available*
eflags         0x203    [ CF IF ]
cs             0x33     51
ss             0x2b     43
ds             0x0      0
es             0x0      0
fs             0x0      0
gs             0x0      0

-- 
Pedro Alves


  reply	other threads:[~2011-02-28 15:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 18:35 Pedro Alves
2011-02-28 15:42 ` Jan Kratochvil
2011-02-28 15:56   ` Pedro Alves [this message]
2011-02-28 18:50     ` Jan Kratochvil
2011-03-18 20:21 ` Pedro Alves
2011-03-21 10:09 ` Regression: " Jan Kratochvil
2011-03-21 20:46   ` Pedro Alves
2011-03-22 14:40   ` Pedro Alves
2011-03-22 15:36     ` Jan Kratochvil
2011-03-22 16:19       ` Pedro Alves
2011-03-21 17:46 ` [commit] Fix tramp-frame.c crash (Re: graceful unwind termination when we'd need unavailable/uncollect memory or registers to unwind further) Ulrich Weigand
2011-03-21 20:52   ` Pedro Alves
2011-03-31 14:43 ` [rfc] Fix broken i386 signal unwinding " Ulrich Weigand
2011-03-31 16:20   ` Pedro Alves
2011-03-31 16:23     ` [rfc] Fix broken i386 signal unwinding (Re: graceful unwind termination when we'd need unavailable/uncollect memory or regis Ulrich Weigand

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=201102281555.56478.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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