[Scribus] Debugging problems with start on OSX

[Michael Crisci]

Andreas,

   Do you want me to do it through Activity Monitor, too?


Michael Crisci


"The older I get, the more I prefer the company of animals."

      - Mark Twain



On Feb 1, 2007, at 12:59 PM, avox wrote:

>
>
>
> 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.
>
> _______________________________________________
> Scribus mailing list
> Scribus at nashi.altmuehlnet.de
> http://nashi.altmuehlnet.de/mailman/listinfo/scribus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://nashi.altmuehlnet.de/pipermail/scribus/attachments/20070201/6064f050/attachment.html