site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Andre On 26-Feb-06, at 17:12 , Brendan Creane wrote: thanks for your help, bcreane _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/ajmas%40sympatico.ca _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Just out of curosity, what are you wanting to do with this information. By understanding the problem it should help find a suitable solution. Has anyone figured out a way to infer the size of an object in the data segment of a Mach-O dynamic library? This is straight-forward under Linux – the dl_info struct, as returned by a call to dladdr (), has a “size_t dli_size” field that reports the size of the nearest symbol. My hope is that there’s an official API to do this, or at least an API that is likely to be supported in the future. My fall-back strategy is to store the size (using sizeof at compile time) in a related symbol. Clunky, but workable. This email sent to ajmas@sympatico.ca This email sent to site_archiver@lists.apple.com