public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: George Anzinger <george@mvista.com>
Cc: amitkale@emsyssoft.com, akpm@osdl.org, pavel@ucw.cz,
	linux-kernel@vger.kernel.org, piggy@timesys.com,
	trini@kernel.crashing.org, mludvig@suse.cz
Subject: Re: kgdb support in vanilla 2.6.2
Date: Thu, 12 Feb 2004 09:33:49 +0100	[thread overview]
Message-ID: <20040212093349.3be06202.ak@suse.de> (raw)
In-Reply-To: <402AD815.6050004@mvista.com>

On Wed, 11 Feb 2004 17:34:13 -0800
George Anzinger <george@mvista.com> wrote:


> > The latest binutils should support .cfi_* for i386 too. I don't see much sense
> > in making the code more ugly just for staying backwards compatible with older versions for the 
> > debug case (without CONFIG_DEBUG_INFO it should be compatible though).
> > You need a fairly new gdb too anyways for it.
> 
> Well, yes, the CVS version I mentioned in my patch is needed as I found a bug in 
> the expression analizer.  I am NOT trying to say compatable with old tools.  I 
> AM trying to do something the CURRENT tools make hard to impossible.
> 
> The problem with the gas CFI support is that it does not provide a way to define 
> CFI expressions which are needed to determine if the CFI address should be zero 
> (i.e. the return is to user space) or the current adjusted stack address.

Michal, can you comment? 
 
> I suppose the open ended .cfi_ thing could be used but it requires that you 
> compute your own sleb128 and uleb128 values.  It is also not clear how you tell 
> this thing if you want a word or a half word as the dwarf2 spec requires.  More 
> info on this would be very "nice".  I really would like to do this with out the 
> dwarf2 macros, but, please understand, one of the main reasons for the effort 
> was to tie off the bottom of the stack and that seems to require an expression 
> capability for the asm code in entry.S.

The one issue that required expression support on x86-64 (switching between the
interrupt stack and the process stack) was handled by a dummy base register
with a single ifdef. This turned out to be relatively clean.

-Andi


  reply	other threads:[~2004-02-12  7:07 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040204230133.GA8702@elf.ucw.cz.suse.lists.linux.kernel>
     [not found] ` <20040204155452.4 9c1eba8.akpm@osdl.org.suse.lists.linux.kernel>
     [not found] ` <20040204152137.500e8319.akpm@osdl.org.suse.lists.linux.kernel>
     [not found]   ` <402182B8.7030900@timesys.com.suse.lists.linux.kernel>
     [not found]     ` <20040204155452.49c1eba8.akpm@osdl.org.suse.lists.linux.kernel>
2004-02-05  3:11       ` kgdb support in vanilla 2.6.2 Andi Kleen
2004-02-05 12:16         ` Pavel Machek
2004-02-05 17:50         ` Amit S. Kale
2004-02-06  2:20           ` Andi Kleen
2004-02-06 11:58             ` Amit S. Kale
2004-02-06 12:16               ` Andi Kleen
2004-02-06 13:05                 ` Amit S. Kale
2004-02-06 13:24                   ` Andi Kleen
2004-02-06 13:44                     ` Amit S. Kale
2004-02-28  0:05                       ` George Anzinger
2004-03-01  9:38                         ` Amit S. Kale
2004-03-02 21:10                           ` George Anzinger
2004-03-02 21:27                             ` Andrew Morton
2004-03-02 23:52                               ` George Anzinger
2004-03-03  5:08                                 ` Amit S. Kale
2004-03-03 16:06                                   ` Tom Rini
2004-03-04  0:42                                   ` George Anzinger
2004-03-03 10:05                               ` Andi Kleen
2004-03-04  0:43                                 ` George Anzinger
2004-03-04  0:50                                   ` Andi Kleen
2004-03-04  5:06                                     ` Amit S. Kale
2004-03-04  5:18                                       ` Andrew Morton
2004-03-04  5:29                                         ` Amit S. Kale
2004-03-04  5:44                                           ` Andrew Morton
2004-03-04 20:54                                           ` George Anzinger
2004-03-04 21:03                                             ` Tom Rini
2004-03-04 23:15                                               ` George Anzinger
2004-03-04 13:01                                         ` Andi Kleen
2004-02-11 14:52                     ` Amit S. Kale
2004-02-10 21:56             ` George Anzinger
2004-02-13 19:42               ` Andi Kleen
2004-02-12  1:34                 ` George Anzinger
2004-02-12  8:33                   ` Andi Kleen [this message]
2004-02-27 21:09               ` Piet Delaney
2004-02-27 21:58                 ` George Anzinger
2004-02-27 23:33                 ` Pavel Machek
2004-02-04 23:01 Pavel Machek
2004-02-04 23:21 ` Andrew Morton
2004-02-04 23:24   ` Pavel Machek
2004-02-04 23:45     ` Andrew Morton
2004-02-04 23:55     ` Tom Rini
2004-02-05  0:16       ` Andrew Morton
2004-02-05  0:23         ` Tom Rini
2004-02-20  0:15         ` George Anzinger
2004-02-04 23:39   ` La Monte H.P. Yarroll
2004-02-04 23:54     ` Andrew Morton
2004-02-05  1:19       ` Pavel Machek
2004-02-20  0:24       ` George Anzinger
2004-02-05  0:39     ` Pavel Machek
2004-02-04 23:52 ` Tom Rini
2004-02-05  0:17   ` Paul Mundt
2004-02-05  0:32     ` Tom Rini

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=20040212093349.3be06202.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=amitkale@emsyssoft.com \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mludvig@suse.cz \
    --cc=pavel@ucw.cz \
    --cc=piggy@timesys.com \
    --cc=trini@kernel.crashing.org \
    /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