Custom Query (1030 matches)

If the image loader can't load an image at its preferred address (presumably because of mmap limitations or something like that), a function named 'relocate_area_contents' is supposed to walk all pointer-bearing areas, adjusting the pointers it finds there by the difference ('bias') between the expected image address and the actual address. I don't know the details, but this doesn't seem to work yet on x8632. (For a long time, it didn't work right on x8664: the code there didn't handle embedded pointers in function objects correctly.)

It's generally proven to be a bad idea to store the CCL directory in the preferences database.

I think that the current thinking is that the CCL directory for a bundled IDE should be initialized in each session to the directory which contains the bundle, and that .dmg distributions should include the .app inside CCL. If someone wants to move the bundle outside of that location, having some mechanism to set the CCL directory for the duration of the current session might be useful (as might be some feedback that indicates that the current setting doesn't look valid.)

Viewing the CCL directory as a persistent global preference creates more problems than it solves (e.g., the persistent preference might point to a stale installation and doesn't generally support environments where different IDE versions are installed, etc.) The proposed default (using the parent directory of the application bundle) is consistent with how the IDE is built and likely to be distributed.

On Fedora 9/PPC, /usr/include/asm/ioctl.h contains:

/* provoke compile error for invalid uses of size argument */
extern unsigned int __invalid_size_argument_for_IOC;
#define _IOC_TYPECHECK(t) \
	((sizeof(t) == sizeof(t[1]) && \
	  sizeof(t) < (1 << _IOC_SIZEBITS)) ? \
	  sizeof(t) : __invalid_size_argument_for_IOC)

/* used to create numbers */
#define _IO(type,nr)		_IOC(_IOC_NONE,(type),(nr),0)
#define _IOR(type,nr,size)	_IOC(_IOC_READ,(type),(nr),(_IOC_TYPECHECK(size)))
#define _IOW(type,nr,size)	_IOC(_IOC_WRITE,(type),(nr),(_IOC_TYPECHECK(size)))

and some ioctl constants are then defined in terms of _IOR(), _IOW(), etc.

The conditional expression in the expansion of _IOC_TYPECHECK (and possibly the reference to the variable) cause the FFI parser to give up, so some IOCTL constants aren't defined.

We can either try to be more ambitious and interpret the expansion (it should always expand to "sizeof(t)" unless there's an error in the header file) or do all macroexpansion as if:

#define _IOC_TYPECHECK(t) sizeof(t)

was predefined and not overridden by the definition in the header file.

(We might be able to translate this particular macro into something that we can make sense of, but we can't always do that, so it seems like a mechanism for dealing with intractable nonsense would be desirable.)