Re: Problems with compilation on Snow leopard for target 10.5
Re: Problems with compilation on Snow leopard for target 10.5
- Subject: Re: Problems with compilation on Snow leopard for target 10.5
- From: Vojtěch Meluzín <email@hidden>
- Date: Sun, 17 Oct 2010 15:41:03 +0200
Well, I don't think that's the case. I just reinstalled Leopard anyway and will check under that one, because so far that was working well. Btw. the same code also works on Win32 & Win64.
Anyway I accidentally didn't include it in the log, but it was access violation at 0xFFFFFFFFC, which means that it just gets NULL. It happened in the first case C++ exception was thrown, so I think this must be a collision of libraries.
Dne 17. října 2010 15:31 Paul Davis
<email@hidden> napsal(a):
2010/10/17 Vojtěch Meluzín <email@hidden>:
> Thanks, but why would I use profiler for it? It seems like GCC only attached
> an uncompatible standard libs to the project. Or more like, GCC compiler
> used 10.5, but linker attached it to 10.6.
valgrind is not a profiler (although that is one thing it can do). it
is primarily a very sophisticated memory access analyzer that can
determine at run time when you overrun array bounds, access freed
memory, and all manner of other nastiness.
your code almost certainly has a bug in it that causes memory
corruption. the corruption makes no (visible) difference under one
combination of compiler/OS libraries, but does under another one.
you're unlikely to find the source of this via introspection.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden