Re: Trapping Console Messages
Re: Trapping Console Messages
- Subject: Re: Trapping Console Messages
- From: Gordon Apple <email@hidden>
- Date: Tue, 21 Apr 2009 20:23:56 -0500
- Thread-topic: Trapping Console Messages
It turns out that the nib-not-loading issue was a bug in my own software in
not properly finding a folder because of running a system on a different
disk.
It also appears that the console message and the crashes I was getting are
likely a system bug in 10.5.6 in that they have gone away in unnamed system
(now that my own bug is fixed, the nibs load, so I can test it).
Unfortunately, I'm not sure I can define it well enough to file a bug report
on 10.5.6.
On 4/21/09 5:35 PM, "Gordon Apple" <email@hidden> wrote:
> I'm not using any of the templates. I was just hoping if I could find out
> wats generating those messages, maybe it would be related to the craches I'm
> having.
>
> I have a data hierarchy window that opens with the document. It is two
> tab-views deep with tabs mostly containing NSTableViews. Two of the messages
> show up after that window is made key and ordered front. Then I have a choice
> of main presentation window: Scrolling-zoomable; non-scrolling resizable;
> borderless full screen. The nibs have only minor differences. Launching the
> scrollable window results in four more of those messages. I can switch
> between window type. This works for a few times, then crashes. Even if I
> keep the same type window and close/open it a few times, it crashes. I'm not
> getting much that is source readable in the stack trace. Those same nibs
> won't even load under an unnamed operating system. I was hoping that would
> yield some more clues as to what is going on here.
>
> Putting a break on malloc_printf gave the following stack trace for the
> messages:
>
> #0 0x94b0c943 in malloc_printf
> #1 0x96c28a6c in auto_collect_internal
> #2 0x96c28b8f in auto_collection_thread
> #3 0x94a5c095 in _pthread_start
> #4 0x94a5bf52 in thread_start
>
>
> On 4/21/09 2:18 PM, "Karl Moskowski" <email@hidden> wrote:
>
>>
>> On 21-Apr-09, at 12:57 PM, Gordon Apple wrote:
>>
>>> Is there a way to trap (or break) when a console message appears, so
>>> one can
>>> look at the stack trace and try to find out where it is coming from?
>>>
>>> After my first document window appears, I get two messages as follows:
>>>
>>> RTP(4643,0xb0103000) malloc: free_garbage: garbage ptr = 0x106e510,
>>> has
>>> non-zero refcount = 1
>>>
>>> RTP is the program. I also get 4 of these messages if I launch
>>> another
>>> window having a scroller, but do not get them for similar windows not
>>> containing a scroller. I am running GC and having a variety of
>>> crashes after
>>> a window is opened and closed a few times, which I'm wondering if is
>>> related
>>> to this message.
>>
>>
>> Are you using any of the template images available in Interface
>> Builder (e.g., NSAddTemplate, NSActionTemplate) in your app. If so,
>> this is a long-known problem in GC apps, and the messages are probably
>> benign.
>> <http://www.cocoabuilder.com/archive/message/cocoa/2007/10/29/191658>
>>
>> ----
>> Karl Moskowski <email@hidden>
>> Voodoo Ergonomics Inc. <http://voodooergonomics.com/>
>>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden