From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jimb@codesourcery.com
Cc: Moqtadir_Mohammed@reyrey.com, gdb@sourceware.org
Subject: Re: Can this be happening?
Date: Tue, 03 Jul 2007 21:54:00 -0000 [thread overview]
Message-ID: <200707032153.l63LrHFA021688@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <m3y7hx2mms.fsf@codesourcery.com> (message from Jim Blandy on Tue, 03 Jul 2007 14:38:51 -0700)
> From: Jim Blandy <jimb@codesourcery.com>
> Date: Tue, 03 Jul 2007 14:38:51 -0700
>
> "Mohammed, Moqtadir" <Moqtadir_Mohammed@reyrey.com> writes:
> > I was trying to look at a core dump of a program, and gdb displays the following result for
> > #info registers
> >
> > eax 0xa0 160
> > ecx 0x2 2
> > edx 0xa 10
> > ebx 0xa7e3de9c -1478238564
> > esp 0xa6babddc 0xa6babddc
> > ebp 0xa6babe00 0xa6babe00
> > esi 0xa7ef9d9a -1477468774
> > edi 0x838f44c 137950284
> > eip 0xa7d85cec 0xa7d85cec <mempcpy+28>
> > eflags 0x50203 [ CF IF RF AC ]
> > cs 0x73 115
> > ss 0x7b 123
> > ds 0x7b 123
> > es 0xb010007b -1341128581
> > fs 0x0 0
> > gs 0x33 51
> >
> > Platform: IA32. (elf)
> >
> > My question is, how is the register 'es' being reported as a 32
> > bit value. I may be completely naive asking this question, but I
> > have been trying to google for anything related to it, but haven't
> > found an answer. Is 'es' not supposed to be only 16bit.
>
> Well, actually, GDB thinks they're all 32 bits long:
Yes, they are, mostly to keep the remote register packet compatible.
They should really be changed into a 16bit type I guess.
Mark
next prev parent reply other threads:[~2007-07-03 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 23:03 Mohammed, Moqtadir
2007-07-03 21:38 ` Jim Blandy
2007-07-03 21:54 ` Mark Kettenis [this message]
2007-07-03 21:58 ` Daniel Jacobowitz
2007-07-05 19:26 ` Balazs Scheidler
2007-07-03 22:16 Mohammed, Moqtadir
2007-07-03 22:46 Mohammed, Moqtadir
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=200707032153.l63LrHFA021688@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=Moqtadir_Mohammed@reyrey.com \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.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