From: Daniel Jacobowitz <drow@false.org>
To: Paul Schlie <schlie@comcast.net>
Cc: Orjan Friberg <orjan.friberg@axis.com>, gdb-patches@sources.redhat.com
Subject: Re: [gdbserver/patch] Z packet support
Date: Sun, 30 Jan 2005 15:38:00 -0000 [thread overview]
Message-ID: <20050130153812.GA5311@nevyn.them.org> (raw)
In-Reply-To: <BE22683E.8D38%schlie@comcast.net>
On Sun, Jan 30, 2005 at 10:32:30AM -0500, Paul Schlie wrote:
> In the spirit of the present structure of the file, might it make
> more sense to actually add decode_Z_packet (... ) to remote-utils.c,
> along with possibly the thread stuff, and use it correspondingly in
> server.c, before it gets out of hand?
>
> And while at it, move CORE_ADDR tweak server.h to wherever it likely
> belongs? (and/or redefine it to void* if more appropriate)?
>
> /* FIXME: This should probably be autoconf'd for. It's an integer type at
> least the size of a (void *). */
> typedef long long CORE_ADDR;
>
>
> And remove redundant declarations from server.h, and include required
> respective headers in server.c
>
> /* Functions from remote-utils.c */
> void decode_M_packet (char *from, CORE_ADDR * mem_addr_ptr,
> unsigned int *len_ptr, char *to);
> ...
> /* Functions from ``signals.c''. */
> ...
>
> ??? (although I know it's easier said than done?)
If you want to make cosmetic structural changes to gdbserver, and
can show that they actually have benefit, then feel free to file a
copyright assignment and submit patches yourself.
As it happens:
1. I don't care either way.
2. Please re-read the comment; it should not be void *. It is also
required that it be harmless for CORE_ADDR to be too large; see
MIPS n32 vs n64.
3. There are nowhere near enough exported functions to justify
proliferating headers.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2005-01-30 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 15:32 Paul Schlie
2005-01-30 15:38 ` Daniel Jacobowitz [this message]
2005-01-30 15:57 ` Paul Schlie
2005-01-30 17:36 ` Daniel Jacobowitz
2005-01-30 19:55 ` Paul Schlie
2005-01-30 20:38 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2004-12-01 15:13 Orjan Friberg
2004-12-07 2:44 ` Daniel Jacobowitz
2004-12-16 18:46 ` Orjan Friberg
2005-01-12 13:35 ` Orjan Friberg
2005-01-30 4:40 ` Daniel Jacobowitz
2005-02-01 12:09 ` Orjan Friberg
2005-02-14 14:42 ` Orjan Friberg
2005-02-24 20:53 ` Daniel Jacobowitz
2005-05-12 12:34 ` Orjan Friberg
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=20050130153812.GA5311@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=orjan.friberg@axis.com \
--cc=schlie@comcast.net \
/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