On Nov 25, 2014, at 9:27 AM, Markus Spoettl wrote:
>
> That hits only one user out of many? All the time, whenever he uses it, and
> no one else. Caused by other apps or ours?
All good points. I'd certainly want a system profile, to examine both it and
the crash report for any 3rd-party kexts
On 25/11/14 15:28, Scott Ribe wrote:
On Nov 25, 2014, at 1:26 AM, Markus Spoettl wrote:
My user says he doesn't experience sluggishness, he also tried rebooting the
machine and repair the disk permissions. Still crashes reliably every time.
In that case, I'd personally suspect heap corrupti
On Nov 25, 2014, at 1:26 AM, Markus Spoettl wrote:
>
> My user says he doesn't experience sluggishness, he also tried rebooting the
> machine and repair the disk permissions. Still crashes reliably every time.
In that case, I'd personally suspect heap corruption.
--
Scott Ribe
scott_r...@elev
On 24/11/14 14:54, Scott Ribe wrote:
So I have no idea if this is related or not. But a few things for you to
possibly find out: is there a lot of file manipulation being done on that
Mac, is performance of everything sluggish before this happens, and will it
work after a reboot.
My user says h
On 24/11/14 14:54, Scott Ribe wrote:
On Nov 24, 2014, at 3:03 AM, Markus Spoettl
wrote:
I'm attaching the call stack of the crash in the hope that someone on the
list recognizes it. Any ideas what might be going on?
Is this 10.10? And the libs are still using FSRef underneath their
implement
On Nov 24, 2014, at 3:03 AM, Markus Spoettl wrote:
>
> I'm attaching the call stack of the crash in the hope that someone on the
> list recognizes it. Any ideas what might be going on?
Is this 10.10? And the libs are still using FSRef underneath their
implementations???
Hoo boy. I've seen 10.
> On 2014 Nov 10, at 15:37, Lee Ann Rucker wrote:
>
> Do you implement any of the delegate methods corresponding to the
> notifications? Cocoa will add notifications for you instead of bothering with
> "respondsToSelector:" all the time.
Thank you, Lee Ann. No, I can’t find any corresponding
Do you implement any of the delegate methods corresponding to the
notifications? Cocoa will add notifications for you instead of bothering with
"respondsToSelector:" all the time.
On Nov 9, 2014, at 5:02 AM, Jerry Krinock wrote:
>
>> On 2014 Nov 07, at 16:02, Greg Parker wrote:
>>
>> You m
> On 2014 Nov 07, at 16:02, Greg Parker wrote:
>
> You may have better luck tracing it from the other side. Run to that line in
> appendToRecentSearches:, set a breakpoint on -[NSNotificationCenter
> postNotificationName:object:userInfo:], and step over your line. At those
> breakpoints you s
> On Nov 7, 2014, at 12:35 PM, Jerry Krinock wrote:
>
>> On 2014 Nov 07, at 14:14, Greg Parker wrote:
>>
>> Which frame are you in when you try to read the register (the top frame, or
>> some other frame)?
>
> Some other. #11 in this call stack:
>
> #0 in strlen ()
> #1 in strdup ()
>
> On 2014 Nov 07, at 14:14, Greg Parker wrote:
>
> Which frame are you in when you try to read the register (the top frame, or
> some other frame)?
Some other. #11 in this call stack:
#0 in strlen ()
#1 in strdup ()
#2 in objc_class::nameForLogging() ()
#3 in cache_t::bad_cache(objc_
> On Nov 7, 2014, at 5:06 AM, Jerry Krinock wrote:
>
>> On 2014 Nov 04, at 01:33, Quincey Morris
>> wrote:
>>
>> The fact that NSNotificationCenter is involved tells you that this is *not*
>> KVO related.
>
> OK, then that makes me even more upset that all I can get from po $rdi, po
> $rdx
> On 2014 Nov 04, at 01:33, Quincey Morris
> wrote:
>
> The fact that NSNotificationCenter is involved tells you that this is *not*
> KVO related.
OK, then that makes me even more upset that all I can get from po $rdi, po
$rdx, po $rcx, etc. when I need them nowadays is those damned “Couldn’
On Nov 3, 2014, at 19:54 , Jerry Krinock wrote:
>
> The highest line in the stack in my code is #12. Line #11 indicates that the
> crash occurs when AppKit attempts to post a notification, which I suspect is
> a KVO notification. (But is NSNotificationCenter used in KVO?)
No, it is not. The
On Jun 17, 2011, at 15:51, Greg Parker wrote:
> On Jun 17, 2011, at 3:48 PM, Laurent Daudelin wrote:
>
>> On Jun 17, 2011, at 15:22, Greg Parker wrote:
>>
>>> On Jun 17, 2011, at 2:40 PM, Laurent Daudelin wrote:
One of my user sent me a crash log with an excerpt here:
...
Ex
On Jun 17, 2011, at 3:48 PM, Laurent Daudelin wrote:
> On Jun 17, 2011, at 15:22, Greg Parker wrote:
>
>> On Jun 17, 2011, at 2:40 PM, Laurent Daudelin wrote:
>>> One of my user sent me a crash log with an excerpt here:
>>>
>>> ...
>>> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
>>> Exception Cod
On Jun 17, 2011, at 15:22, Greg Parker wrote:
> On Jun 17, 2011, at 2:40 PM, Laurent Daudelin wrote:
>> One of my user sent me a crash log with an excerpt here:
>>
>> ...
>> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
>> Exception Codes: KERN_INVALID_ADDRESS at 0x0027
>> ...
>> Thread 4
On Jun 17, 2011, at 2:40 PM, Laurent Daudelin wrote:
> One of my user sent me a crash log with an excerpt here:
>
> ...
> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0x0027
> ...
> Thread 4 Crashed: Dispatch queue: com.apple.root.default-priori
Hi Andrew,
I did think about that.
I've poked around in Contextual Menu Items and Input Methods folders
and can't find anything there. I don't have LCC installed, and I
avoid installing anything that uses APE. I have just had a quick
check and can't see any evidence that APE has been ins
Hi, Brett,
Is it possible that you have any haxies, or any Input Managers, of any
sort installed? Logitech Control Center, for instance, or perhaps
APE? That's the only thing that I could think of that might be
yielding such a crash.
Cheers,
Andrew
On May 13, 2008, at 9:21 PM,
20 matches
Mail list logo
