Re: Bizarre x86 segment layout problem causing select() slowdown: solved, sort of
Re: Bizarre x86 segment layout problem causing select() slowdown: solved, sort of
- Subject: Re: Bizarre x86 segment layout problem causing select() slowdown: solved, sort of
- From: Steve Sisak <email@hidden>
- Date: Wed, 7 Feb 2007 15:53:20 -0500
At 11:22 AM -0800 2/7/07, Dave Hayden wrote:
On Feb 7, 2007, at 10:56 AM, glenn andreas wrote:
32768 ends up being smack in the middle of the __TEXT segment, so
whatever is at that address is part of the program. Thus adding
dummy routines will change what part of the program that points to,
and thus alter the behavior.
Yeah, and when it's at that "magic" value, the contents of
(int*)32768 is 583, what I was seeing returned from read().
Well, I'm going to go crawl under a rock now.. Thanks for your help, everyone.
Someone really should collect this thread up into a "Kon and Bal's
Puzzle Page".
This has been an entertaining saga to follow.
-Steve
(For those new to Mac development, Apple used to publish a _very_
high quality quarterly magazine called "develop", edited by Caroline
Rose, which featured a regular programing/debugging puzzle in the
form of a conversation between 2 programmers -- your score starts at
100 and decreases as they reveal more details of the problem)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden