Skip to content
New issue

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

Core dump #45

Open
skrew opened this issue Jan 7, 2015 · 8 comments
Open

Core dump #45

skrew opened this issue Jan 7, 2015 · 8 comments
Assignees
Labels

Comments

@skrew
Copy link

skrew commented Jan 7, 2015

Hi, i have a core dump when i try to use it on a iOS app compiled with armv7, i don't know if it's working with iOS bin ?

0  fracture-cl     0x0000000001b150eb llvm::sys::PrintStackTrace(_IO_FILE*) + 38
1  fracture-cl     0x0000000001b15368
2  fracture-cl     0x0000000001b14d0d
3  libpthread.so.0 0x00007f16fccef340
4  fracture-cl     0x00000000009de01d
5  fracture-cl     0x00000000009dd6cf main + 463
6  libc.so.6       0x00007f16fbcedec5 __libc_start_main + 245
7  fracture-cl     0x00000000009db5b4
@rtc-draper
Copy link
Collaborator

What does it pop up as when you run “file” on it? Even if not recognized, the raw/dummy object file format should be defaulted to…

Can you run in a debugger and provide line information? What you have is the default stack trace and that’s not helpful. Note you’ll need to set your debugger to follow fork calls.

-R

From: eric@skrobs [mailto:[email protected]]
Sent: Tuesday, January 06, 2015 7:14 PM
To: draperlaboratory/fracture
Subject: [fracture] Core dump (#45)

Hi, i have a core dump when i try to use it on a iOS app compiled with armv7, i don't know if it's working with iOS bin ?

0 fracture-cl 0x0000000001b150eb llvm::sys::PrintStackTrace(_IO_FILE*) + 38

1 fracture-cl 0x0000000001b15368

2 fracture-cl 0x0000000001b14d0d

3 libpthread.so.0 0x00007f16fccef340

4 fracture-cl 0x00000000009de01d

5 fracture-cl 0x00000000009dd6cf main + 463

6 libc.so.6 0x00007f16fbcedec5 __libc_start_main + 245

7 fracture-cl 0x00000000009db5b4


Reply to this email directly or view it on GitHubhttps://github.com//issues/45.


Notice: This email and any attachments may contain proprietary (Draper non-public) and/or export-controlled information of Draper Laboratory. If you are not the intended recipient of this email, please immediately notify the sender by replying to this email and immediately destroy all copies of this email.


@skrew
Copy link
Author

skrew commented Jan 7, 2015

Mach-O universal binary with 1 architecture: [arm_v7: Mach-O arm_v7 executable]

For the debugger, you mean on fracture-cl, not the ios binaries, right ?
Seem to have a problem while getting arch... but i pass -arch=arm

Program received signal SIGSEGV, Segmentation fault.
0x00000000009de01d in loadBinary (FileName=...) at fracture-cl.cpp:174
174     TT.setArch(Triple::ArchType(TempExecutable->getArch()));

Don't know if you have enough information, i'm on linux and without xcode / ida ... i'm (near) lost ;)

@rtc-draper
Copy link
Collaborator

That’s enough.

This indicates it’s trying to set the target triple and causing llvm’s libraries to choke. It might be us, though…Can you give me a dummy MachO binary to play with (e.g., hello world?)--- then we can have a test case and get it working. TBH we’ve never tried it on iOS stuff, although in theory you should be able to open it in “raw” mode.

From: eric@skrobs [mailto:[email protected]]
Sent: Tuesday, January 06, 2015 7:32 PM
To: draperlaboratory/fracture
Cc: Carback, Richard T., III
Subject: Re: [fracture] Core dump (#45)

Mach-O universal binary with 1 architecture: [arm_v7: Mach-O arm_v7 executable]

For the debugger, you mean on fracture-cl, not the ios binaries, right ?
Seem to have a problem while getting arch... but i pass -arch=arm

Program received signal SIGSEGV, Segmentation fault.

0x00000000009de01d in loadBinary (FileName=...) at fracture-cl.cpp:174

174 TT.setArch(Triple::ArchType(TempExecutable->getArch()));

Don't know if you have enough information, i'm on linux and without xcode / ida ... i'm (near) lost ;)


Reply to this email directly or view it on GitHubhttps://github.com//issues/45#issuecomment-68960285.


Notice: This email and any attachments may contain proprietary (Draper non-public) and/or export-controlled information of Draper Laboratory. If you are not the intended recipient of this email, please immediately notify the sender by replying to this email and immediately destroy all copies of this email.


@skrew
Copy link
Author

skrew commented Jan 7, 2015

running with -arch=arm -triple=arm-unknown-unknown got a new error

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
MCDirector: Using Triple: arm-unknown-unknown
MCDirector: Using CPU: generic
MCDirector: Using Features: 

Program received signal SIGSEGV, Segmentation fault.
0x0000000000a05675 in fracture::Disassembler::Disassembler (this=0x2e0c8e0, NewMC=0x2e0d000, NewExecutable=0x0, NewModule=0x0, InfoOut=..., ErrOut=...) at Disassembler.cpp:31
31      TheModule = new Module(Executable->getLoadName(), *MC->getContext());
(gdb) bt
#0  0x0000000000a05675 in fracture::Disassembler::Disassembler (this=0x2e0c8e0, NewMC=0x2e0d000, NewExecutable=0x0, NewModule=0x0, InfoOut=..., ErrOut=...) at Disassembler.cpp:31
#1  0x00000000009de388 in loadBinary (FileName=...) at fracture-cl.cpp:190
#2  0x00000000009dd6cf in main (argc=4, argv=0x7fffffffe318) at fracture-cl.cpp:844

Look like a bad news for me... Anyway, thanks

@rtc-draper
Copy link
Collaborator

For arm, typically you need to specify the attr version with “-mattr=v7” or the like. I’m not sure which attr is appropriate for iPhone HW.

Anyway, send us a sample and I’ll see what I can do to make it readable.

From: eric@skrobs [mailto:[email protected]]
Sent: Tuesday, January 06, 2015 7:49 PM
To: draperlaboratory/fracture
Cc: Carback, Richard T., III
Subject: Re: [fracture] Core dump (#45)

running with -arch=arm -triple=arm-unknown-unknown got a new error

#0 0x0000000000a05675 in fracture::Disassembler::Disassembler (this=0x2e0c8e0, NewMC=0x2e0d000, NewExecutable=0x0, NewModule=0x0, InfoOut=..., ErrOut=...) at Disassembler.cpp:31

#1 0x00000000009de388 in loadBinary (FileName=...) at fracture-cl.cpp:190

#2 0x00000000009dd6cf in main (argc=4, argv=0x7fffffffe318) at fracture-cl.cpp:844

Look like a bad new for me... Anyway, thanks


Reply to this email directly or view it on GitHubhttps://github.com//issues/45#issuecomment-68961792.


Notice: This email and any attachments may contain proprietary (Draper non-public) and/or export-controlled information of Draper Laboratory. If you are not the intended recipient of this email, please immediately notify the sender by replying to this email and immediately destroy all copies of this email.


@rtc-draper
Copy link
Collaborator

Marking as bug for now. I'll ask around and see if someone can generate an iPhone example for us.

@skrew
Copy link
Author

skrew commented Jan 7, 2015

I can send to you the sample i use, tell me where to send you a (private) dropbox link... Also if you want a custom build from iOS i can make one for you.

@rtc-draper
Copy link
Collaborator

A "helloworld" program for iOS posted to github would be best.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants