|
|
7.
|
|
|
Cannot create a file in which to save the backtrace
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:107
|
|
|
12.
|
|
|
Cannot open file %1 for writing
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:138
|
|
|
14.
|
|
|
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.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:147
|
|
|
17.
|
|
|
As the usage of these options is not recommended - because they can, in rare cases, be responsible for KDE problems - a backtrace will not be generated.
You need to turn these options off and reproduce the problem again in order to get a backtrace.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:181
|
|
|
18.
|
|
|
Backtrace will not be created.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:186
|
|
|
23.
|
|
|
KDE crash handler gives the user feedback if a program crashed
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
main.cpp:43
|
