[Scribus] Debugging problems with start on OSX

[avox]

Michael Crisci wrote:
> 
> I got a new answer:
> 
> ...
> (gdb) Quit
> 
no quit here...


> (gdb) bt
> #0  0xdeadbeec in ?? ()
> Cannot access memory at address 0xdeadbeec
> Cannot access memory at address 0x0
> Cannot access memory at address 0xdeadbeec
> Cannot access memory at address 0xdeadbeec
> #1  0xdeadbeef in ?? ()
> Cannot access memory at address 0xdeadbeec
> Cannot access memory at address 0x0
> warning: Previous frame identical to this frame (corrupt stack?)
> Cannot access memory at address 0xdeadbeec
> Cannot access memory at address 0xdeadbeec
> #2  0xdeadbeef in ?? ()
> Cannot access memory at address 0x0
> warning: Previous frame identical to this frame (corrupt stack?)
> Cannot access memory at address 0x8
> 

Thanks Michael!

That definitely looks like dead beef; waiting will not help here.
My guess is a linking problem.

Now I'd be interested in the list of open files from Activity Monitor... :-)

/Andreas
-- 
View this message in context: http://www.nabble.com/-Scribus--Debugging-problems-with-start-on-OSX-tf3155432.html#a8753472
Sent from the Scribus mailing list archive at Nabble.com.