Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA/RFC Prec] Add Linux AMD64 process record support second  	version, (AMD64 Linux system call support) 3/3
Date: Wed, 15 Jul 2009 16:52:00 -0000	[thread overview]
Message-ID: <daef60380907150221n25c4364l7f257a24601f7413@mail.gmail.com> (raw)
In-Reply-To: <4A5CE59A.8080208@vmware.com>

On Wed, Jul 15, 2009 at 04:07, Michael Snyder<msnyder@vmware.com> wrote:
> Hui,
>
> It looks like amd64-tdep.c is going to need an epilogue unwinder,
> similar to the one in i386-tdep.c.  Can you add one, maybe using
> the 386 one as a model?
>
> I haven't checked in the infrun change that makes use of it,
> but when I do, this will break.
>

OK.  I will.


And about infrun code, without the arch support.  It will break,right?

What about add a check for "frame_unwind_caller_id" in infrun?  If it
got something wrong or arch don't support it.  Use the way in
http://sourceware.org/ml/gdb-patches/2009-07/msg00182.html to handle
it.

Then we will not worry about the arch doesn't have unwinder.

What do you think about it?


Thanks,
Hui


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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  2:40 Hui Zhu
2009-07-13  3:32 ` Michael Snyder
2009-07-17 12:45   ` Hui Zhu
2009-07-18  3:08     ` Michael Snyder
2009-07-19 17:19       ` Hui Zhu
2009-07-20  0:57         ` Michael Snyder
2009-07-19 21:03       ` Hui Zhu
2009-07-20  2:31         ` Michael Snyder
2009-07-20 14:13           ` Hui Zhu
2009-07-25 21:05             ` Michael Snyder
2009-07-26  1:14         ` Michael Snyder
2009-07-28 11:22           ` Hui Zhu
2009-08-03  5:41             ` Hui Zhu
2009-08-09 22:58               ` Michael Snyder
2009-08-10  3:15                 ` Hui Zhu
2009-08-13  5:43                   ` Michael Snyder
2009-07-14 22:19 ` Michael Snyder
2009-07-15 16:52   ` Hui Zhu [this message]

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=daef60380907150221n25c4364l7f257a24601f7413@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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