mikeash / maobjcruntime Goto Github PK

Hi,

Just wanted to double check this awesome library is deployable to app store.

It's really well written, I use it alot to understand how the runtime works. I didn't realize how dynamic ObjC was until I used your library to runtime inspect how UIAppearance works in iOS5.

Nice work!

-CV

i got error while compiling in my project.

Would this fit in your library?

Man, sorry for asking here since I cannot ask issue from the page of PLC;
I'm using your popular repository:
https://github.com/plausiblelabs/plcrashreporter

What I'm doing now is monitor cpu/gpu/memory programmatically(not monitoring crash, since there already many 3rd party lib can do that, what I'm monitoring is app's performance);

For example, when cpu overloads, I'll dump the backtrace of the suspicious thread with BSBacktraceLogger ,also I use your PLC to catch the whole trace info.

What I get is like this, by PLC:

And by BSBacktraceLogger:

But seems none of above stack trace can help me to analyze and find how the performance issue happens.

Generally, when we are using 3rd party "crash report" platform, we can see crash log like following, with clear line number, method, etc, which can help very much in specifying and locating issue (I know it's symboled by atos):

But now my app is not crashing, just memory overloads, no crash log;
I just want to locate where or which thread or what action that caused the occasional low performance;
Am I wrong? or How can I better analyze the stack trace? Man

I can't seem to invoke methods that have arguments which are not 4-bytes (i.e. BOOL, CGSize, etc...). It works fine with NSInteger, CGFloat and objects. Is this a known limitation?

It always aborts at the line checking if(inSize != sigSize) in RTMethod.m

I get the following error when compiling a project that has this library as a dependency:

MAObjCRuntime/RTProtocol.m:79:13: Definition of 'Protocol' must be imported from module 'ObjectiveC.Protocol' before it is required

It seems to only happen with XCode 7.3, running 7.2 side by side compiles and runs just fine. Wondering if something changed in 7.3 or the compiler that causes these issues?

Works fine for x86-64, but fails when built+run as i386:
2011-11-27 17:18:34.254 MAObjCRuntime[4644:a0f] Testing TestSubclasses
2011-11-27 17:18:34.263 MAObjCRuntime[4644:a0f] TestSubclasses: SUCCESS
2011-11-27 17:18:34.264 MAObjCRuntime[4644:a0f] Testing TestCreateClass
2011-11-27 17:18:34.264 MAObjCRuntime[4644:a0f] TestCreateClass: SUCCESS
2011-11-27 17:18:34.265 MAObjCRuntime[4644:a0f] Testing TestMetaclass
2011-11-27 17:18:34.266 MAObjCRuntime[4644:a0f] TestMetaclass: SUCCESS
2011-11-27 17:18:34.266 MAObjCRuntime[4644:a0f] Testing TestSetSuperclass
2011-11-27 17:18:34.267 MAObjCRuntime[4644:a0f] TestSetSuperclass: SUCCESS
2011-11-27 17:18:34.268 MAObjCRuntime[4644:a0f] Testing TestInstanceSize
2011-11-27 17:18:34.268 MAObjCRuntime[4644:a0f] TestInstanceSize: SUCCESS
2011-11-27 17:18:34.269 MAObjCRuntime[4644:a0f] Testing TestSetClass
2011-11-27 17:18:34.270 MAObjCRuntime[4644:a0f] TestSetClass: SUCCESS
2011-11-27 17:18:34.270 MAObjCRuntime[4644:a0f] Testing TestMethodList
2011-11-27 17:18:34.271 MAObjCRuntime[4644:a0f] TestMethodList: SUCCESS
2011-11-27 17:18:34.272 MAObjCRuntime[4644:a0f] Testing TestAddMethod
2011-11-27 17:18:34.272 MAObjCRuntime[4644:a0f] TestAddMethod: SUCCESS
2011-11-27 17:18:34.273 MAObjCRuntime[4644:a0f] Testing TestMethodFetching
2011-11-27 17:18:34.275 MAObjCRuntime[4644:a0f] TestMethodFetching: SUCCESS
2011-11-27 17:18:34.275 MAObjCRuntime[4644:a0f] Testing TestSetMethod
2011-11-27 17:18:34.278 MAObjCRuntime[4644:a0f] TestSetMethod: SUCCESS
2011-11-27 17:18:34.279 MAObjCRuntime[4644:a0f] Testing TestProtocolQuery
2011-11-27 17:18:34.280 MAObjCRuntime[4644:a0f] TestProtocolQuery:189: assertion failed: [[protocol incorporatedProtocols] containsObject: [RTProtocol protocolWithObjCProtocol: NSProtocolFromString(@"NSObject")]]
2011-11-27 17:18:34.280 MAObjCRuntime[4644:a0f] TestProtocolQuery: FAILED
2011-11-27 17:18:34.281 MAObjCRuntime[4644:a0f] Testing TestIvarQuery
2011-11-27 17:18:34.282 MAObjCRuntime[4644:a0f] TestIvarQuery: SUCCESS
2011-11-27 17:18:34.286 MAObjCRuntime[4644:a0f] Testing TestPropertyQuery
2011-11-27 17:18:34.289 MAObjCRuntime[4644:a0f] TestPropertyQuery: SUCCESS
2011-11-27 17:18:34.290 MAObjCRuntime[4644:a0f] Testing TestIvarAdd
2011-11-27 17:18:34.291 MAObjCRuntime[4644:a0f] TestIvarAdd: SUCCESS
2011-11-27 17:18:34.292 MAObjCRuntime[4644:a0f] Testing TestEquality
2011-11-27 17:18:34.292 MAObjCRuntime[4644:a0f] TestEquality: SUCCESS
2011-11-27 17:18:34.293 MAObjCRuntime[4644:a0f] Testing TestMessageSending
2011-11-27 17:18:34.293 MAObjCRuntime[4644:a0f] TestMessageSending: SUCCESS
2011-11-27 17:18:34.294 MAObjCRuntime[4644:a0f] Testing TestMessageSendingNSObjectCategory
2011-11-27 17:18:34.297 MAObjCRuntime[4644:a0f] TestMessageSendingNSObjectCategory: SUCCESS
2011-11-27 17:18:34.298 MAObjCRuntime[4644:a0f] Tests complete: FAILED: 1 total assertion failure

The Xcode project in my fork make it easy to repro: just switch to the i386 executable.

this can resolved by runtime？

Thanks for this great work! The RTProperty class has seeded a library I've been using heavily in a project. This library been useful enough that I've been thinking about releasing it. The library consists of a few classes, one of which is based off of RTProperty (but has grown a bit since then). I'm currently planning on using an MIT license, but which license is not something I feel strongly about. Before I released it, I wanted to check with you:

1. that this was ok with you,
2. what sort of attribution you would want, if any,
3. if you had any other comments.

Thanks again for your work! It's made the objc runtime libraries far more approachable.

James