We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When running oslog, it prints out the following text:
root@Campbells-iPhone ~# oslog Apr 17 22:05:09 Campbells-iPhone: ====== fish: Job 1, 'oslog' terminated by signal SIGSEGV (Address boundary error)
Running with LLDB exposes a call to dyld3::MachOFile::hasLoadCommand:
dyld3::MachOFile::hasLoadCommand
root@Campbells-iPhone ~# lldb oslog (lldb) target create "oslog" Current executable set to 'oslog' (arm64). (lldb) r Process 5303 launched: '/var/jb/usr/bin/oslog' (arm64) Process 5303 stopped * thread #1, stop reason = EXC_BAD_ACCESS (code=50, address=0x10249782c) frame #0: 0x000000010249782c dyld`dyld3::MachOFile::hasLoadCommand(unsigned int) const dyld`dyld3::MachOFile::hasLoadCommand: -> 0x10249782c <+0>: pacibsp 0x102497830 <+4>: sub sp, sp, #0x90 0x102497834 <+8>: stp x22, x21, [sp, #0x60] 0x102497838 <+12>: stp x20, x19, [sp, #0x70] Target 0: (oslog) stopped.
The text was updated successfully, but these errors were encountered:
@campbellcole bt all
bt all
Sorry, something went wrong.
Try otool -L path/to/oslog
It should show the LC_LOAD_COMMANDs
No branches or pull requests
When running oslog, it prints out the following text:
Running with LLDB exposes a call to
dyld3::MachOFile::hasLoadCommand
:The text was updated successfully, but these errors were encountered: