FROM : Ewan Delanoy
DATE : Thu Apr 05 19:17:32 2007
Hello all,
I have a Cocoa text-editor project that compiles without warning and
appearantly runs fine.
However, the debugger issues a warning that I feel I should take very
seriously :
libMallocDebug[Schreiben-1007]: frame pointer goes from bffed260 to
bfffd2e0 -- assuming invalid.
I was not able to track the bug very precisely, all I know is that :
-it is triggered when the app prints a document (or just saves it to PDF)
-in the debugger's ``pseudo-console", the warning above is repeated n times,
where n is the number of pages in the document.
From what I see in Google, the "frame pointer" seems to be a well-known
piece
of data in C/Objective-C, but that's too technical for me ...
Can anyone help me out on this ? TIA,
Ewan
DATE : Thu Apr 05 19:17:32 2007
Hello all,
I have a Cocoa text-editor project that compiles without warning and
appearantly runs fine.
However, the debugger issues a warning that I feel I should take very
seriously :
libMallocDebug[Schreiben-1007]: frame pointer goes from bffed260 to
bfffd2e0 -- assuming invalid.
I was not able to track the bug very precisely, all I know is that :
-it is triggered when the app prints a document (or just saves it to PDF)
-in the debugger's ``pseudo-console", the warning above is repeated n times,
where n is the number of pages in the document.
From what I see in Google, the "frame pointer" seems to be a well-known
piece
of data in C/Objective-C, but that's too technical for me ...
Can anyone help me out on this ? TIA,
Ewan
| Related mails | Author | Date |
|---|---|---|
| No related mails found. | ||






Cocoa mail archive

