I'm able to build the plugin and even start Adium and login. The buddy list show's people online and then crashes. I don't know if the information below helps in the slightest, but this has been an issue since early this month. I don't recall the git snapshot I'm currently using, but would be willing to track it down if need be.
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000010329565
0x00007fff8daf843e in strstr ()
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure if Adium offers the -debug switch. That would narrow it down to the message the core is currently processing.
If you can use gdb and/or valgrind then that will make easier to narrow down the crash site. It helps to compile the code with -O0 when debugging. You'll need the -g option to get debugging information into the binary.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is a debug. I'm not sure if this is enough detail. Let me know if it's not. I think this makes sense in terms of when I was looking at the GIT tree. Buddy Icons are new and I think before them I was ok.
Doesn't show line number or function parameters. Did you compile the code with -O0 -g? Maybe you need to run Adium inside a debugger to get a valid backtrace.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm able to build the plugin and even start Adium and login. The buddy list show's people online and then crashes. I don't know if the information below helps in the slightest, but this has been an issue since early this month. I don't recall the git snapshot I'm currently using, but would be willing to track it down if need be.
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000010329565
0x00007fff8daf843e in strstr ()
I'm not sure if Adium offers the -debug switch. That would narrow it down to the message the core is currently processing.
If you can use gdb and/or valgrind then that will make easier to narrow down the crash site. It helps to compile the code with -O0 when debugging. You'll need the -g option to get debugging information into the binary.
There is a debug. I'm not sure if this is enough detail. Let me know if it's not. I think this makes sense in terms of when I was looking at the GIT tree. Buddy Icons are new and I think before them I was ok.
18:51:55: Buddy icon update for sip:robert.hawkins@diebold.com
18:51:55:
18:51:55: -:76: Exception raised: Uncaught system exception: signal 11
18:51:55: 0 Adium 0x00000001004f53de AILogBacktrace_impl + 54
1 Adium 0x0000000100060e49 Adium + 396873
2 ExceptionHandling 0x00000001009f29e2 - + 168
3 ExceptionHandling 0x00000001009f27ba NSExceptionHandlerUncaughtSignalHandler + 35
4 libsystem_c.dylib 0x00007fff8b9d68ea _sigtramp + 26
5 ??? 0x0000000111167c38 0x0 + 4581653560
6 SIPEAdiumPlugin 0x000000010d271610 http_conn_input + 2197
7 AdiumLibpurple 0x000000010041aa87 __adium_input_add_block_invoke_0 + 70
8 libdispatch.dylib 0x00007fff8982a0b6 _dispatch_client_callout + 8
9 libdispatch.dylib 0x00007fff8982c29b _dispatch_source_invoke + 691
10 libdispatch.dylib 0x00007fff8982b305 _dispatch_queue_invoke + 72
11 libdispatch.dylib 0x00007fff8982f091 _dispatch_main_queue_callback_4CF + 220
12 CoreFoundation 0x00007fff8fb9d0fe __CFRunLoopRun + 1614
13 CoreFoundation 0x00007fff8fb9c6b2 CFRunLoopRunSpecific + 290
14 HIToolbox 0x00007fff8f7340a4 RunCurrentEventLoopInMode + 209
15 HIToolbox 0x00007fff8f733e42 ReceiveNextEventCommon + 356
16 HIToolbox 0x00007fff8f733cd3 BlockUntilNextEventMatchingListInMode + 62
17 AppKit 0x00007fff88916613 _DPSNextEvent + 685
18 AppKit 0x00007fff88915ed2 - + 128
19 AppKit 0x00007fff8890d283 - + 517
20 AppKit 0x00007fff888b1cb6 NSApplicationMain + 869
21 Adium 0x0000000100002184 Adium + 8580
Doesn't show line number or function parameters. Did you compile the code with -O0 -g? Maybe you need to run Adium inside a debugger to get a valid backtrace.
FYI,
I just downloaded/compiled commit a1ac1c4694bb717510746f8fa6e8af34cd29d722 tagged "Release 1.14.1 - Bug Fixes I" and I don't have a problem anymore.