Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: IBM S/390 prologue analysis revisited
Date: Tue, 01 Jul 2003 00:57:00 -0000	[thread overview]
Message-ID: <3F00DC8C.5040908@redhat.com> (raw)
In-Reply-To: <vt2d6gv2lt3.fsf@zenia.home>

> I'd like to revisit the question of how to proceed with the s390 frame
> unwinding / prologue analysis code.  I'd like to commit my prologue
> analysis changes, but the IBM GDB folks have expressed a general
> interest in keeping the prologue analysis logic minimal and using
> Dwarf CFI everywhere.  So I'd like to outline my reasons, and see what
> the community thinks is the best approach to take.

You mean: [just for the record]: new prologue analyzer for S/390
http://sources.redhat.com/ml/gdb-patches/2003-04/msg00352.html

I thought the conclusion was that it could/should go in anyway.

As for IBM and the s390.

http://www10.software.ibm.com/developerworks/opensource/linux390/current2_4_19-may2002.shtml#debug20030416
> Note: This patch changes gdb common code in a manner that might cause problems for other platforms. Use the debugger sources created by appyling this patch only to build a debugger for the s390 or s390x architectures.

Yes, someone needs to get CFI working, but that isn't the way to do it :-(

Andrew



  parent reply	other threads:[~2003-07-01  0:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <vt2d6gv2lt3.fsf@zenia.home>
     [not found] ` <1030630233621.ZM27669@localhost.localdomain>
2003-07-01  0:14   ` Elena Zannoni
2003-07-01  0:57 ` Andrew Cagney [this message]
2003-07-01 12:28   ` Andrew Cagney
2003-07-02  0:06     ` Jim Blandy
2003-07-02 18:33       ` Andrew Cagney
2003-07-02 19:20         ` Daniel Jacobowitz
2003-07-01 22:51   ` Jim Blandy

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=3F00DC8C.5040908@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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