MallocDebug invalid frame pointer messages
MallocDebug invalid frame pointer messages
- Subject: MallocDebug invalid frame pointer messages
- From: "Adam R. Maxwell" <email@hidden>
- Date: Sun, 08 Jun 2008 21:31:07 -0700
I'm posting here since the message is from the debugging tools, but if
there's a better place, please let me know! I'm seeing a bunch of
messages like the following:
libMallocDebug[FileView Program-27775]: frame pointer goes from
b0923678 to b09336c8 -- assuming invalid.
when running a test app under MallocDebug via Xcode. Running with
libMallocDebug in gdb with a breakpoint on MDprintf, I find it's being
printed in URL loading code (see below...it apparently only happens
when I'm loading a .webarchive file).
Is this something to worry about? I've recently started seeing random
crashes, so I've been trying to use MallocDebug to look for overruns.
The message sounds like something's smashing the stack, but I can't
find it documented anywhere.
thanks,
Adam
Breakpoint 1, 0x0006596e in MDprintf ()
(gdb) bt
#0 0x0006596e in MDprintf ()
#1 0x0006647e in getBacktrace ()
#2 0x00067e56 in MDmalloc_zone_malloc ()
#3 0x960d71df in _CFURLConnectionPushClientEvent ()
#4 0x960d940b in connDidReceiveResponse ()
#5 0x96122625 in sendDidReceiveResponse ()
#6 0x960f978e in fileReadStreamCB ()
#7 0x935c05e9 in _CFStreamSignalEventSynch ()
#8 0x935ae60e in CFRunLoopRunSpecific ()
#9 0x935aecf8 in CFRunLoopRunInMode ()
#10 0x90f56460 in +[NSURLConnection(NSURLConnectionReallyInternal)
_resourceLoadLoop:] ()
#11 0x90ef2f1d in -[NSThread main] ()
#12 0x90ef2ac4 in __NSThread__main__ ()
#13 0x9686c6f5 in _pthread_start ()
#14 0x9686c5b2 in thread_start ()
(gdb) c
Continuing.
libMallocDebug[FileView Program-27775]: frame pointer goes from
b0923678 to b09336c8 -- assuming invalid.
_______________________________________________
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