corefiles/2281: es segment register shows up as 32bit on IA32 based core file

[Moqtadir_Mohammed@ReyRey.com]

>Number:         2281
>Category:       corefiles
>Synopsis:       es segment register shows up as 32bit on IA32 based core file
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 02 22:28:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     Moqtadir Mohammed
>Release:        6.6
>Organization:
>Environment:
IA32, Debian-Linux kernel:2.6.21.3, ELF executable
>Description:
An application crashed with SIGBUS, while analyzing the core dump, I run the following command:
#info registers

The interesting thing to note in the output is that the
register 'es' is printed as a 32bit value, while infact it can never be greater than 16bits.
Ouput follows, will provide more info if needed, the core file is 32 megs in size, if need to be attached just let me know.

The output of 'info registers' is

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

Thanks,
Moqtadir

Completely out of topic note:
One of the interesting thing to note, completely out of topic, is that even though SIGBUS is not supposed happen on IA32, this crash happens in memcpy with the movl not being on a 4 byte boundary (which is always the case, but crash happens once in 6 months).
>How-To-Repeat:
Not reproducible
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: