Crash when printing on Mac

[Lubomir I. Ivanov]

On 18 July 2014 13:15, Robert Helling <helling at lmu.de> wrote:
>
> On 18.07.2014, at 12:08, Lubomir I. Ivanov <neolit123 at gmail.com> wrote:
>
> Lubomir,
>
> you could try setting a breakpoint in the PrintDialog constructor and
> stepping trough.
>
>
> What would I be looking for? The debugger integration in Qt Creator is quite
> nice. I can run until the exception and the at all levels of the stack look
> at the code and local variables. What would single stepping reveal in
> addition?
>

you've mentioned "But the exception seems to be thrown before that is
tried to be accessed", so i'm not sure.
i'm guessing we are looking for a library call that triggers the SIGBUS.

seriously doubt it's our code that is directly causing bad memory access.

>
> this may require a "set dont-handle-bad-access 1" in GDB depending if
> how OSX decides to trow a signal if one of it's core libraries fails.
>
>
> Hmm. I don’t quite see how that would be relevant. And apple got rid of gdb
> in favour of lldb as well (but the integration with Creator works never the
> less).
>

i have never used the tool in question and wasn't aware that GDB was
replaced by it.

> Could this be due to me still using Qt4?
>

well, we should support Qt4 in general.
please, post your OSX version so that others can test as well.

lubomir
--