trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: June 2012

How to make proper backtraces?

From: Dexter Filmore <Dexter.Filmore@...>
Date: Fri, 1 Jun 2012 20:27:22 +0200
Can't trace crashes. What would I need for, let's say, kopete.
Is there a general approach?


This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents 
creation of proper backtraces, or the stack frame was seriously corrupted in 
the crash.

passprompt
ptrace: Kein passender Prozess gefunden.

/home/dexter/11345: Datei oder Verzeichnis nicht gefunden.

/home/dexter/.trinity/tmp-shodan/drkonqiPJG8gE.tmp:1: Error in sourced command 
file:
No stack.



-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

Attachments: