Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>,
	muller@cerbere.u-strasbg.fr, autophile@starband.net
Cc: gdb@sources.redhat.com, cgf@redhat.com
Subject: Re: [Q] Accessing fs:0 on x86 Linux?
Date: Sat, 15 Dec 2001 10:04:00 -0000	[thread overview]
Message-ID: <3C1B9099.5020306@cygnus.com> (raw)
In-Reply-To: <1438-Sat15Dec2001193204+0200-eliz@is.elta.co.il>


> I looked into this issue when GDB 5.1 was in the last stages of
> development, but eventually decided that GDB lacked some
> infrastructure to add such a functionality.  You could find the
> traces of that in a thread "Re: 8 bit read"; start reading here:
> 
>  http://sources.redhat.com/ml/gdb/2001-07/msg00338.html


Can I suggest playing with the @<blah> prefix operator that Michael 
Snyder recently added.

It added a framework for specifying something like ``(int @code *)0''. 
This indicates a pointer in the code space.  The intent is for the 
mechanism to be extended to support more than just code and data spaces.

An initial pass at this would have:

	(@fs*)0

One possible follow-on would be to change $fs's type to ``(uint8 @fs 
*)'' so that ``x/b $fs + 5'' did the right thing.

I should note that the current implementation is restricted to just 
@code and @data so some ground work would be needed.

Andrew


  reply	other threads:[~2001-12-15 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13 16:55 Robert Baruch
2001-12-14  0:38 ` Pierre Muller
2001-12-14  7:53   ` Robert Baruch
2001-12-15  9:33   ` Eli Zaretskii
2001-12-15 10:04     ` Andrew Cagney [this message]
2001-12-16  0:15       ` Eli Zaretskii

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=3C1B9099.5020306@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=autophile@starband.net \
    --cc=cgf@redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=muller@cerbere.u-strasbg.fr \
    /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