From: George Anzinger <george@mvista.com>
To: Pavel Machek <pavel@suse.cz>
Cc: "Amit S. Kale" <amitkale@emsyssoft.com>,
Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
Tom Rini <trini@kernel.crashing.org>,
KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>
Subject: Re: [Kgdb-bugreport] Re: kgdb: rename i386-stub.c to kgdb.c
Date: Wed, 25 Feb 2004 13:17:15 -0800 [thread overview]
Message-ID: <403D10DB.8060506@mvista.com> (raw)
In-Reply-To: <20040225103703.GB6206@atrey.karlin.mff.cuni.cz>
Pavel Machek wrote:
> Hi!
>
>
>>>kgdb uses really confusing names for arch-dependend parts. This fixes
>>>it. Okay to commit?
>>
>>Why is arch/$x/kernel/$x-stub.c confusing? The name $x-stub.c is indicative of
>>architecture dependent code in it. Err, well so is the path.
>
>
>
> Well, looking at i386-stub.c, how do you know it is kgdb-related?
>
>
>>PPC and sparc stubs in present vanilla kernel use this naming convention.
>>That's why I adopted it.
>>
>>I find kernel/kgdbstub.c, arch/$x/kernel/$x-stub.c more consistent compared to
>>kernel/kgdbstub.c, arch/$x/kernel/kgdb.c
>
>
> I actually made it kernel/kgdb.c and arch/*/kernel/kgdb.c. I believe
> there's no point where one could be confused....
gdb itself gets confused with this. Try, for example, time.c which, on the x86,
is in both arch and common code. I use emacs with kgdb and it gets confused
when I point at a location in the source and tell it to set a break point.
Please, lets have only one of each name.
--
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
next prev parent reply other threads:[~2004-02-25 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 13:06 kgdb: rename i386-stub.c to kgdb.c Pavel Machek
2004-02-25 7:33 ` Amit S. Kale
2004-02-25 10:37 ` Pavel Machek
2004-02-25 10:59 ` Amit S. Kale
2004-02-25 11:10 ` Pavel Machek
2004-02-25 11:23 ` Amit S. Kale
2004-02-25 21:17 ` George Anzinger [this message]
2004-02-25 21:25 ` [Kgdb-bugreport] " Pavel Machek
2004-02-25 21:28 ` Tom Rini
2004-02-25 22:31 ` George Anzinger
2004-02-26 4:24 ` Daniel Jacobowitz
2004-02-26 23:07 ` George Anzinger
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=403D10DB.8060506@mvista.com \
--to=george@mvista.com \
--cc=amitkale@emsyssoft.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=pavel@ucw.cz \
--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