From professional translators, enterprises, web pages and freely available translation repositories.
backtrace browser
comment
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
backtrace loaded.
منشأیاب
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
backtrace not possible
تÙÙÛØ¯ ÙØ´Ùد
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
backtrace navigation tool view
name
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
crash information (backtrace)
@ info/ rich
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
backtrace will not be created.
منشأیاب ایجاد نمیشود.
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
unable to create a valid backtrace.
قادر به ایجاد یک منشأیاب معتبر نیست.
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
backtrace of the crash i am sending:
@ info/ rich
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
it was not possible to generate a backtrace.
تÙÙÛØ¯
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
could not generate a backtrace as the debugger '%1 'was not found.
چون اشکالزدای »% 1 « یافت نشد ، نتوانست یک منشأیاب ایجاد کند. debugging finished
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
once you get a useful backtrace (or if you do not want to install the missing debugging packages) you can continue.
@ title
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
this page will generate a "backtrace" of the crash. this is information that tells the developers where the application crashed.
@ info/ rich
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
Warning: Contains invisible HTML formatting
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.
به نظر میرسد که این منشأیاب بیمصرف است. احتمالاً ، به این دلیل بستههای شما به روشی ساخته میشوند ، که از ایجاد منشأیاب مناسب جلوگیری کنند ، و یا اینکه قاب پشته به طور جدی در فروپاشی خراب شود.
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
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
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
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
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
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
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
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.
کاربرد این گزینهها توصیه نمیشود - زیرا در اندک مواردی میتوانند پاسخگوی مشکلات kde باشند - منشأیابی تولید نخواهد شد. باید این گزینهها را خاموش کرده و به منظور به دست آوردن منشأیاب ، مسئله را دوباره ایجاد کنید.
Last Update: 2011-10-23
Usage Frequency: 1
Quality: