You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, can't load a mach fat binary (because which one do we load?), so we need some kind of picker/selector, which presents the user a list of the architectures, which the user selects, which then loads that binary.
This seems mostly a QML issue (which I'm not good at, hoping someone will grab this issue).
So to sketch out a basic approach (which I haven't thought too consciously about), for starters, once a mach fat is selected (which should sent the mach-fat request kind), can iterate through arches with something like:
Hint::MachFat(_) => {let multi = mach::MultiArch::new(&bytes)?;let arches = multi.arches()?;
And then display the arches as appropriate to the user (need a new UI selector or something here)
The user will then select the architecture (which can simply be an index), and the mach-o binary can then be extracted and loaded via:
// this is the ith archlet bytes = arch.slice(bytes)?;
loader::load_mach(bytes,0,NameOfBinary)
which gets routed appropriately somehow ;)
Or something like that; there are several possible avenues here
The text was updated successfully, but these errors were encountered:
Hmmm yea that's probably the easiest. Perhaps we should make the disassembly step after loading lazy though as loading several architectures eagerly probably doesn't make a lot of sense. Perhaps disassembler fires when a program element first receives focus ?
Yea, I was specifically worried about the i386 and x86_64 fat binaries, which are usually the system libraries like libSystem_B.dylib, et. al. Seems a waste to load the i386 and x86_64 eagerly, especially for larger binaries.
Currently, can't load a mach fat binary (because which one do we load?), so we need some kind of picker/selector, which presents the user a list of the architectures, which the user selects, which then loads that binary.
This seems mostly a QML issue (which I'm not good at, hoping someone will grab this issue).
So to sketch out a basic approach (which I haven't thought too consciously about), for starters, once a mach fat is selected (which should sent the
mach-fat
request kind), can iterate through arches with something like:And then display the arches as appropriate to the user (need a new UI selector or something here)
The user will then select the architecture (which can simply be an index), and the mach-o binary can then be extracted and loaded via:
which gets routed appropriately somehow ;)
Or something like that; there are several possible avenues here
The text was updated successfully, but these errors were encountered: