|
9.
|
|
|
A file named "%1" already exists. Are you sure you want to overwrite it?
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:123
|
|
10.
|
|
|
Overwrite File?
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:125
|
|
11.
|
|
|
&Overwrite
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:126
|
|
12.
|
|
|
Cannot open file %1 for writing
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:138
|
|
13.
|
|
|
Unable to create a valid backtrace.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:146
|
|
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
|
|
15.
|
|
|
Loading backtrace...
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:156
|
|
16.
|
|
|
The following options are enabled:
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:179
|
|
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
|