Sie suchten nach: backtrace (Englisch - Kurdisch)

include backtrace
beriya şandina raporê divê ravekirinê binivîsî.

backtrace loaded.
& Çewtî nûsaf bike

backtrace not possible
dixwazî dîtina paşde biafirînî? ev ji bo pêşdebiran dibe alîkar ku karibin bibînin ka çi çewt e mixabin ev ê di makîneyên hêdî de dem bigire. nîşe: dîtina paşde nîşan nade ka çewtî bi temamî çi ye û çawa derketiye. rastkirina çewtiyan bêyî raveyeke giştî ya di derbarê têkçûnê de pêk nayê.

crash information (backtrace)
@ info/ rich

backtrace will not be created.
dîtina paşde tê barkirin...

unable to create a valid backtrace.
bi vê navê% 1 jixwe pelek heye. ji dil dixwazî bi ser vê pelê binivîsî?

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

it was not possible to generate a backtrace.
sepan têk çû sepana% appname têk çû.

you might want to fix your program. take a look at the backtrace below.
gihandina dûrname

could not generate a backtrace as the debugger '%1 'was not found.
jibergirtin

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.
li ser pelî binivîse?

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.
wisa xuya ye ku ev dîtina paşde bi kar nayne. dibe ku ev ji ber astengiya dîtina paşde a pakêtan\\ be an jî çarçoveya sergoyê xerab bûbe.