upports 64 bit or not. So if
> you're kernel is running in 32 bit mode, then certain AVX instructions will
> be interpreted differently than if the kernel is running 64 bit.
>
> http://en.wikipedia.org/wiki/VEX_prefix
>
> Best regards,
>
> Element
>
>
> O
well,
I installed glib as --universal, meaning that it contains both 32 bits and 64
bits binaries. And actually, I removed the 64 bit binary (using the lipo
function), because Director is a 32 bits application and all Xtras (plugins)
are also. So we are really running in 32 bit here. Even on Mac
0x34894bc, Element…
Anyway…
Le 22 août 2013 à 17:33, a...@gratin.org a écrit :
>> You should be able to do that like:
>> x/8bx 0x039894bc
>>
>
> (gdb) x/8bx 0x039894bc
> 0x39894bc:0xe10xee0xee0xee0
Le 21 août 2013 à 16:41, Element Green a écrit :
> You should be able to do that like:
> x/8bx 0x039894bc
>
(gdb) x/8bx 0x039894bc
0x39894bc: 0xe10xee0xee0xee0xe10xee0xee0xee
>
> Do you know any details about the differences in the CPUs? Maybe th
Just as a precision. On my machine, I disassembled the function _after_
starting the program. Not before. For what it is worth. In case it makes a
difference in the thinking.
++ as :: Antoine Schmitt :: iPhone
Le 21 août 2013 à 15:11, "a...@gratin.org" a écrit :
> I just ran t
Well,
remember that the core dump was from a Mac system on which glib crashes. The
same app does not crash on most systems, including mine.
I just ran the app on gdb on my system, and disassembled the same function
(before running the program). This showed to the same instructions as in the
core
Hi,
so I moved along with this problem, analyzing the core dump.
Unfortunately, I did not have the symbols of glib (it seems that 'brew install
--test glib' did not build a debug version of glib despite what the doc says).
But I could disassemble the faulty function :
Dump of assembler code for
Sorry, this is a typo. I meant 2.36.3.
Thank you for all the advices. I will seek to have a core dump and try to find
the fault instruction. Will keep you updated.
Cheers !
Le 20 août 2013 à 01:26, Element Green a écrit :
> I built it against glib 2.26.3, using homebrew, by doing a "brew in
Hello,
Le 16 août 2013 à 18:58, Element Green a écrit :
>
> I had a look at the thread_memory_from_self() function in the glib
> source code and I don't see anything that would suggest usage of SSE
> instructions (its a memory allocation function). There is a lot of
> use of the thread system
Hello,
trying to build a debug version of glib, and will do some tests on the failing
target machines.
In the meantime, I wanted to note that when I compile fluidsynth against the
latest glib (v2.36.3), I get a lot a deprecation warnings related to mutex and
threads :
/Users/antoine/Documents
Hi list,
I have a difficult bug.
I'm building a Adobe Director Xtra, which is a kind of plugin, i.e. a
dynamically loaded library, incorporating fluidsynth.
This is on Mac OSX.
I build this Xtra on my MacOSX 10.8.4 system (Xcode 4.3). Fluidsynth is build
as a static library and is statically link
11 matches
Mail list logo
