From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] New inf-procfs module (replacing procfs)
Date: Fri, 13 Jan 2006 20:28:00 -0000 [thread overview]
Message-ID: <200601132027.k0DKRvSf021579@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060113173921.GJ10275@adacore.com> (message from Joel Brobecker on Fri, 13 Jan 2006 21:39:21 +0400)
> Date: Fri, 13 Jan 2006 21:39:21 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> Note about inf-procfs. I think certain comments should be reformatted,
> but I have deliberatly left them alone for now, to minimize the size
> of the diff. Will take care of that later. Also, building this file
> generates some warnings, some of them being related to the move to
> gdb_byte. I will also take care of that later for the same reason.
Hmm, when Andrew converted infptrace.c into inf-ptrace.c and even more
so when I converted infttrace.c into inf-ttrace.c we took the
opportunity, to do some serious cleanup. In a way, the introduction
of these files offers a unique opportunity to clean things up target
by target. And I really think procfs.c is in need of such a cleanup.
Right now it's a maze of #ifdefs; there are also some Solaris-related
improvements that should be made, but that I haven't done yet, because
I'm too afraid of breaking other targets.
It'd be great if you would be willing to do the cleanup. If not,
could you give me two weeks to finish my (barely started) attempt to
do it?
Mark
next prev parent reply other threads:[~2006-01-13 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 17:40 Joel Brobecker
2006-01-13 20:28 ` Mark Kettenis [this message]
2006-01-14 3:33 ` Joel Brobecker
2006-01-27 20:10 ` Michael Snyder
2006-01-27 20:33 ` Joel Brobecker
2006-01-27 21:46 ` Michael Snyder
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=200601132027.k0DKRvSf021579@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.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