On Wed, 21 Aug 2013, Element Green wrote:
Time to look at the actual machine code,
Or maybe get a new gdb and hope that it can put an opcode to the
instruction.
Although as far as I know most CPUs should be 64 bit capable these days.
I dunno. It looks like x86 Macs can pack anything fro
On Wed, Aug 21, 2013 at 7:11 AM, a...@gratin.org wrote:
> 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
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 the app on gdb o
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
On 08/21/2013 01:37 PM, a...@gratin.org wrote:
> 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 di
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
