On 08/30/2013 04:48 PM, Alexander Thurgood wrote:
I'm seeing this in my master builds of LO on startup :
Program received signal SIGTRAP, Trace/breakpoint trap.
0x7fff5fc01028 in __dyld__dyld_start ()
(gdb) bt full
#0 0x7fff5fc01028 in __dyld__dyld_start ()
No symbol table info
Le 02/09/13 11:33, Stephan Bergmann a écrit :
And that (unrelated) one is fixed now with
0e40013d909c5b28f9d37cf7370fceed1a6ae891 Add macosx_x86_64 extension
platform identifier.
Oh, excellent, thanks !
Alex
___
LibreOffice mailing list
Hi all,
I'm seeing this in my master builds of LO on startup :
Program received signal SIGTRAP, Trace/breakpoint trap.
0x7fff5fc01028 in __dyld__dyld_start ()
(gdb) bt full
#0 0x7fff5fc01028 in __dyld__dyld_start ()
No symbol table info available.
#1 0x0001 in ?? ()
No
I'm seeing this in my master builds of LO on startup :
Program received signal SIGTRAP, Trace/breakpoint trap.
0x7fff5fc01028 in __dyld__dyld_start ()
The application will continue to load in gdb if I continue,
I think this is perfectly normal, I see it all the time, too, if I gdb
Le 30/08/13 17:20, Tor Lillqvist a écrit :
Hi Tor,
I think this is perfectly normal, I see it all the time, too, if I gdb
soffice right after a fresh build. soffice re-execs itself when starting
for the first time after an upgrade to a new version (including just a
build after a fresh
