Usted buscó: backtrace (Inglés - Galés)

backtrace browser
comment

backtrace loaded.
& olrhain

backtrace navigation tool view
name

crash information (backtrace)
@ info/ rich

backtrace will not be created.
a ydych am greu olrheiniad? fe fydd hyn o gymorth i ddatblygwyr i ganfod beth aeth o' i le. yn anffodus cymer hyn gryn amser ar beiriannau araf. noder: nid yw olhreiniad yn cymryd lle disgrifiad cywir o' r nam a gwybodaeth ar sut i' w ail- achosi. nid yw' n bosib i gywiro' r nam heb ddisgrifiad cywir.

unable to create a valid backtrace.
methu creu olrheiniad dilys.

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

you might want to fix your program. take a look at the backtrace below.
mae' r cymhwysiad% progname (% appname), pid% pid, wedi cwympo gan achosi' r arwydd% signum (% signame). name

could not generate a backtrace as the debugger '%1 'was not found.
methu creu ôlrhain, gan na chanfuwyd y dadnamydd '% 1' debugging finished

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.
ymddengys na ellir defnyddio' r olrheiniad yma. mwy na thebyg, yr achos yw bod eich pecynnau yn cael eu adeiladu mewn ffordd sy' n atal creu olrheiniadau iawn, neu roedd y ffrâm pentwr yn cael ei lygru yn ddifrifol yn y chwalfa.

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.
chwalodd y cymhwysiad chwalodd y rhaglen% appname.