From: Daniel Jacobowitz <drow@mvista.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] gdbserver bits
Date: Thu, 18 Jul 2002 09:24:00 -0000 [thread overview]
Message-ID: <20020718153509.GA24669@nevyn.them.org> (raw)
In-Reply-To: <3D36DFC4.6060406@suse.cz>
On Thu, Jul 18, 2002 at 05:33:24PM +0200, Michal Ludvig wrote:
> Daniel Jacobowitz wrote:
> >Go ahead. Doesn't GDB have the same problem with CS and SS?
>
> Well, yes actually. But in GDB it doesn't make problems, because there
> the regbuf is zeroed after allocation so it cannot happen, that you'd
> write something wrong to CS or SS (at least on x86-64 the kernel doesn't
> permit setting CS since it uses it for it's own purposes).
> Consider cleaning the newly allocated regbuf in gdbserver as well...
I don't think I will; writing arbitrary zeros is just as damaging as
writing a bad regset. The whole thing needs to be set.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-07-18 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 8:08 Michal Ludvig
2002-07-18 8:33 ` Daniel Jacobowitz
2002-07-18 8:35 ` Michal Ludvig
2002-07-18 9:24 ` Daniel Jacobowitz [this message]
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=20020718153509.GA24669@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
/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