Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, dje@google.com, msnyder@vmware.com,
		dan@codesourcery.com, eliz@gnu.org
Subject: Re: [RFA] i386 segment base support
Date: Thu, 20 May 2010 12:54:00 -0000	[thread overview]
Message-ID: <AANLkTinTyjpzOvvv3lOdalnhoV1g41YkdA6y27NTpnHR@mail.gmail.com> (raw)
In-Reply-To: <201005200819.o4K8JseL023478@glazunov.sibelius.xs4all.nl>

On Thu, May 20, 2010 at 16:19, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>> From: Hui Zhu <teawater@gmail.com>
>> Date: Thu, 20 May 2010 15:34:17 +0800
>>
>> Hi guys,
>>
>> I update the old patch that I post to support segment base value.
>
> Sorry, but we still need to discuss what programming model you intend
> to support before I will consider looking at diffs.
>
> Currently, on i386, GDB supports a fully flat 32-bit model, with one
> small exception on platforms that support thread-local-storage.  In
> that model you can assume that all the segment bases are 0 except for
> %gs.  If that's all that people are interested in, I don't think we
> should bother with segment bases for %cs, %ds, %es, %fs and %ss.
>
> If people want to support fully segmented memory in GDB, then what you
> propose is probably not enough, at least not for 32-bit mode.
>

I have a very, very need the value of segment base register.  Do you
have some good idea to put this value from target part
(i386-linux-nat) to gdbarch part (prec)?

Thanks,
Hui


  reply	other threads:[~2010-05-20  8:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20  7:45 Hui Zhu
2010-05-20  8:40 ` Mark Kettenis
2010-05-20 12:54   ` Hui Zhu [this message]
2010-05-20 14:41   ` Daniel Jacobowitz
2010-05-20 14:44     ` Mark Kettenis
2010-05-20 15:30       ` Daniel Jacobowitz
2010-05-21  5:29       ` Hui Zhu

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=AANLkTinTyjpzOvvv3lOdalnhoV1g41YkdA6y27NTpnHR@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=dan@codesourcery.com \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=msnyder@vmware.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