[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: %gs:0 thread pseudoregister in oskit-mach
From: |
Roland McGrath |
Subject: |
Re: %gs:0 thread pseudoregister in oskit-mach |
Date: |
Tue, 23 Apr 2002 16:01:12 -0400 (EDT) |
> No, the assert happens using the DS segment. Hmm, I guess something
> more is wrong here. It looks like the segment isn't protecting us here
> and the segmentation fault just happens because of there is nothing
> mapped at 0xc0000000 and it gets a page fault. If the segment would
> protect us we should get a general protection exception, right?
Yes, I think that's what should happen. However, I think the segment
limits are all off by one. That is, try accessing 0xc0000004. If that is
the only problem, then using VM_MAX_ADDRESS-VM_MIN_ADDRESS-1 in the
fill_ldt_descriptor calls should fix it.
- %gs:0 thread pseudoregister in oskit-mach, Roland McGrath, 2002/04/07
- Re: %gs:0 thread pseudoregister in oskit-mach, Jeroen Dekkers, 2002/04/20
- Re: %gs:0 thread pseudoregister in oskit-mach, Roland McGrath, 2002/04/21
- Re: %gs:0 thread pseudoregister in oskit-mach, Jeroen Dekkers, 2002/04/23
- Re: %gs:0 thread pseudoregister in oskit-mach, Jeroen Dekkers, 2002/04/23
- Re: %gs:0 thread pseudoregister in oskit-mach, Roland McGrath, 2002/04/23
- Re: %gs:0 thread pseudoregister in oskit-mach, Jeroen Dekkers, 2002/04/23
- Re: %gs:0 thread pseudoregister in oskit-mach, Roland McGrath, 2002/04/23
- Re: %gs:0 thread pseudoregister in oskit-mach, Jeroen Dekkers, 2002/04/23
- Re: %gs:0 thread pseudoregister in oskit-mach,
Roland McGrath <=
- Re: %gs:0 thread pseudoregister in oskit-mach, Jeroen Dekkers, 2002/04/23
- Re: %gs:0 thread pseudoregister in oskit-mach, Roland McGrath, 2002/04/23
- Re: %gs:0 thread pseudoregister in oskit-mach, Roland McGrath, 2002/04/23