Hi Jean-Daniel, Thanks for the response - would you know how to go about determining what some of those public functions are? Unfortunately I'm looking to read the RAM from a game - so I guarantee those functions/memory offsets are not publicly disclosed.
Or a way to randomly read offsets to determine what they contain etc.... I know windows has some applications which will attach to others and show which modules are loaded and some public information - but I'm quite new to the OS X development space so not sure where to search for these types of applications. Thanks again! On Tue, Aug 12, 2008 at 1:33 PM, Jean-Daniel Dupas <[EMAIL PROTECTED]>wrote: > > In practice, it's perfectly possible to access other processes memory using > public functions (it require some privileges since 10.4 intel). > But to do it you have to use the low-level mach API and that's off topic > here. > > And no, code injection is not used only by virus. (see > http://rentzsch.com/mach_star/ ) > > > Le 12 août 08 à 19:18, Negm-Awad Amin a écrit : > > >> Am Di,12.08.2008 um 19:01 schrieb Mike Abdullah: >> >> You can't do this. Each application runs in its own protected memory. >>> >> Sometimes you can do this: >> http://en.wikipedia.org/wiki/Computer_virus >> ;-) >> >> Serious: There are techniques to get acccess to another application memory >> under some circumstances. None of them is related to Cocoa since there is no >> class named NSVirus. >> >> Amin >> >> >> >>> >>> On 12 Aug 2008, at 17:04, Josh wrote: >>> >>> All, >>>> >>>> I'm trying to get started w/viewing/editing/interacting with the memory >>>> of >>>> another running application but I'm not where to get started. You could >>>> think of this as being a simple "game trainer" - which basically allows >>>> you >>>> to view and edit values in memory. >>>> >>>> Can anyone point me to where I should get started? Function >>>> names/examples >>>> would be a GREAT help - I haven't had experience with hooking into >>>> another >>>> application's memory. >>>> >>>> Thanks!!!! >>>> _______________________________________________ >>>> >>>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >>>> >>>> Please do not post admin requests or moderator comments to the list. >>>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >>>> >>>> Help/Unsubscribe/Update your Subscription: >>>> >>>> http://lists.apple.com/mailman/options/cocoa-dev/cocoadev%40mikeabdullah.net >>>> >>>> This email sent to [EMAIL PROTECTED] >>>> >>> >>> _______________________________________________ >>> >>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >>> >>> Please do not post admin requests or moderator comments to the list. >>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >>> >>> Help/Unsubscribe/Update your Subscription: >>> http://lists.apple.com/mailman/options/cocoa-dev/negm-awad%40cocoading.de >>> >>> This email sent to [EMAIL PROTECTED] >>> >> >> Amin Negm-Awad >> [EMAIL PROTECTED] >> >> >> >> >> _______________________________________________ >> >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >> >> Please do not post admin requests or moderator comments to the list. >> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >> >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/cocoa-dev/devlists%40shadowlab.org >> >> This email sent to [EMAIL PROTECTED] >> >> > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]