Vous avez cherché: backtrace (Anglais - Xhosa)

backtrace browser
name=umkhangeli zincwadi we lancomment

backtrace loaded.
ayikwazi ukwenza uphando lwasemva.

backtrace navigation tool view
name

crash information (backtrace)
@ info/ rich

backtrace will not be created.
yenzekile.

unable to create a valid backtrace.
ufuna ukwenza uphando lwasemva? oku kuzakunceda ababhekisi phambili uku bana phandle okuhambe ngokungalunganga. ngelishwa oku kuzakuthatha ixesha elithile kwiimatshini ezicothayo. qaphela: u phando lwasemva alumelanga inkcazelo eyiyo yebug kwaye ulwazi lokuyivelisa. akukho lula ukulungisa ibug ngaphandle kwenkcazelo eyiyo.

backtrace of the crash i am sending:
@ info/ rich

you might want to fix your program. take a look at the backtrace below.
izicwangciso ezikhetiweyo zababhekisi phambiliname

could not generate a backtrace as the debugger '%1 'was not found.
& uphando lwasemva

once you get a useful backtrace (or if you do not want to install the missing debugging packages) you can continue.
@ title

this page will generate a "backtrace" of the crash. this is information that tells the developers where the application crashed.
@ info/ rich

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.
quka uphando lwasemva

another debugging process is attached to the crashed application. therefore, the drkonqi debugger cannot fetch the backtrace. please close the other debugger and click reload crash information.
@ info

use this button to reload the crash information (backtrace). this is useful when you have installed the proper debug symbol packages and you want to obtain a better backtrace.
@ action: button

the reporting assistant is disabled because the crash handler dialog was started in safe mode. you can manually report this bug to %1 (including the backtrace from the developer information tab.)
@ info

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.
uphando lwasemva alwenzeki