Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michal Ludvig <mludvig@suse.cz>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] gdbserver bits
Date: Thu, 18 Jul 2002 08:35:00 -0000	[thread overview]
Message-ID: <3D36DFC4.6060406@suse.cz> (raw)
In-Reply-To: <20020718150834.GA29860@nevyn.them.org>

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...

Michal Ludvig
-- 
* SuSE CR, s.r.o     * mludvig@suse.cz
* +420 2 9654 5373   * http://www.suse.cz


  reply	other threads:[~2002-07-18 15:33 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 [this message]
2002-07-18  9:24     ` Daniel Jacobowitz

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=3D36DFC4.6060406@suse.cz \
    --to=mludvig@suse.cz \
    --cc=drow@mvista.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