public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "Amit S. Kale" <amitkale@emsyssoft.com>,
	Powerpc Linux <linuxppc-dev@lists.linuxppc.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>
Subject: Re: PPC KGDB changes and some help?
Date: Wed, 21 Jan 2004 15:12:25 -0800	[thread overview]
Message-ID: <400F0759.5070309@mvista.com> (raw)
In-Reply-To: <20040121192128.GV13454@stop.crashing.org>

Tom Rini wrote:
> On Wed, Jan 21, 2004 at 11:42:17AM -0700, Tom Rini wrote:
> 
>>On Wed, Jan 21, 2004 at 10:23:12PM +0530, Amit S. Kale wrote:
>>
>>
>>>Hi,
>>>
>>>Here it is: ppc kgdb from timesys kernel is available at
>>>http://kgdb.sourceforge.net/kgdb-2/linux-2.6.1-kgdb-2.1.0.tar.bz2
>>>
>>>This is my attempt at extracting kgdb from TimeSys kernel. It works well in 
>>>TimeSys kernel, so blame me if above patch doesn't work.
>>
>>Okay, here's my first patch against this.
> 
> 
> And dependant upon this is a patch to fixup the rest of the common PPC
> code, as follows:
> - Add FRAME_POINTER
> - Put the bits of kgdbppc_init into ppc_kgdb_init.
> - None of the gen550 stuffs depend on CONFIG_8250_SERIAL directly,
>   remove that constraint.
> - Add missing bits like debuggerinfo, BREAKPOINT, etc.
> - Add a kgdb_map_scc machdep pointer.
> 
> --- 1.48/arch/ppc/Kconfig	Wed Jan 21 10:13:13 2004
> +++ edited/arch/ppc/Kconfig	Wed Jan 21 12:18:32 2004
> @@ -1405,6 +1405,14 @@
>  	  Say Y here only if you plan to use some sort of debugger to
>  	  debug the kernel.
>  	  If you don't debug the kernel, you can say N.
> +
> +config FRAME_POINTER
> +	bool "Compile the kernel with frame pointers"
> +	help
> +	  If you say Y here the resulting kernel image will be slightly larger
> +	  and slower, but it will give very useful debugging information.
> +	  If you don't debug the kernel, you can say N, but we may not be able
> +	  to solve problems without frame pointers.

This is fast becoming old hat.  If you compile with dwarf debug info, you not 
only get more reliable frame info, but you do not need frame pointers.  Gdb is 
almost there.  The languages have already arrived.

A question I have been meaning to ask:  Why is the arch/common connection via a 
structure of addresses instead of just calls?  I seems to me that just calling 
is a far cleaner way to do things here.  All the struct seems to offer is a way 
to change the backend on the fly.  I don't thing we ever want to do that.  Am I 
missing something?

-g

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  parent reply	other threads:[~2004-01-21 23:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040120172708.GN13454@stop.crashing.org>
     [not found] ` <200401211946.17969.amitkale@emsyssoft.com>
     [not found]   ` <20040121153019.GR13454@stop.crashing.org>
2004-01-21 16:53     ` PPC KGDB changes and some help? Amit S. Kale
2004-01-21 18:42       ` Tom Rini
2004-01-21 19:21         ` Tom Rini
2004-01-21 19:22           ` Tom Rini
2004-01-22 17:44             ` Tom Rini
2004-01-22 18:05               ` Tom Rini
2004-01-23 22:46                 ` Tom Rini
2004-01-23 23:38                   ` George Anzinger
2004-01-26 20:46                     ` Tom Rini
2004-01-26 21:27                       ` George Anzinger
2004-01-26 21:42                         ` Tom Rini
2004-01-26 22:35                           ` George Anzinger
2004-01-26 21:45                       ` George Anzinger
2004-01-26 22:06                         ` Tom Rini
2004-01-27  9:05                           ` Amit S. Kale
2004-01-24  0:48                   ` George Anzinger
2004-01-24  3:47                   ` [PATCH] Kgdb dwarf2 for asm George Anzinger
2004-01-27 18:22                   ` PPC KGDB changes and some help? Tom Rini
2004-01-21 22:03           ` Tom Rini
2004-01-21 23:12           ` George Anzinger [this message]
2004-01-22 15:07             ` Tom Rini
2004-01-22 15:25               ` Hollis Blanchard
2004-01-22 15:45                 ` Tom Rini
2004-01-22 16:06                   ` Amit S. Kale
2004-01-22 16:45                     ` Tom Rini
2004-01-22 22:46                       ` George Anzinger
2004-01-22 22:52                         ` Tom Rini
2004-01-22 23:09                           ` George Anzinger
2004-01-22 22:35                     ` George Anzinger
2004-01-23 17:08                     ` Tom Rini
2004-01-22 21:54                   ` George Anzinger
2004-01-26 21:32           ` Tom Rini
2004-01-27  8:59             ` Amit S. Kale
2004-01-21 23:05         ` George Anzinger
2004-01-22 15:03           ` 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=400F0759.5070309@mvista.com \
    --to=george@mvista.com \
    --cc=amitkale@emsyssoft.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --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