mirror of
https://github.com/varun-r-mallya/sysprof.git
synced 2025-12-31 20:36:25 +00:00
Update Polish help translation
This commit is contained in:
@ -7,8 +7,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: sysprof-help\n"
|
||||
"POT-Creation-Date: 2017-06-28 17:59+0000\n"
|
||||
"PO-Revision-Date: 2017-07-02 18:44+0200\n"
|
||||
"POT-Creation-Date: 2017-09-25 16:15+0000\n"
|
||||
"PO-Revision-Date: 2017-09-27 12:40+0200\n"
|
||||
"Last-Translator: Piotr Drąg <piotrdrag@gmail.com>\n"
|
||||
"Language-Team: Polish <community-poland@mozilla.org>\n"
|
||||
"Language: pl\n"
|
||||
@ -371,13 +371,18 @@ msgstr ""
|
||||
"z jądra Linux. Może to mieć wiele przyczyn, na przykład <em>wywołanie "
|
||||
"systemowe</em> lub <em>sygnał</em>."
|
||||
|
||||
#. (itstool) path: page/title
|
||||
#: C/faq.page:9
|
||||
msgid "What does heap mean?"
|
||||
msgstr "Co oznacza „heap”?"
|
||||
|
||||
#. (itstool) path: section/title
|
||||
#: C/faq.page:10
|
||||
#: C/faq.page:12
|
||||
msgid "What does \"In file [heap]\" mean?"
|
||||
msgstr "Co oznacza „In file [heap]”?"
|
||||
|
||||
#. (itstool) path: section/p
|
||||
#: C/faq.page:12
|
||||
#: C/faq.page:14
|
||||
msgid ""
|
||||
"This means that sysprof believes a function was called from somewhere in the "
|
||||
"program's heap (where <code>malloc</code> allocates memory) rather than the "
|
||||
@ -389,12 +394,12 @@ msgstr ""
|
||||
"zwykle znajduje się kod wykonywalny). Jest kilka możliwych wyjaśnień."
|
||||
|
||||
#. (itstool) path: section/title
|
||||
#: C/faq.page:19
|
||||
#: C/faq.page:22
|
||||
msgid "JIT (Just in Time) compilers"
|
||||
msgstr "Kompilatory JIT"
|
||||
|
||||
#. (itstool) path: section/p
|
||||
#: C/faq.page:21
|
||||
#: C/faq.page:24
|
||||
msgid ""
|
||||
"Languages like Java can generate executable code while a program is running "
|
||||
"and store it in the heap. Sysprof is accurately reporting the situation in "
|
||||
@ -405,12 +410,12 @@ msgstr ""
|
||||
"sytuację."
|
||||
|
||||
#. (itstool) path: section/title
|
||||
#: C/faq.page:27
|
||||
#: C/faq.page:30
|
||||
msgid "Optimizing compilers"
|
||||
msgstr "Kompilatory optymalizujące"
|
||||
|
||||
#. (itstool) path: section/p
|
||||
#: C/faq.page:29
|
||||
#: C/faq.page:32
|
||||
msgid ""
|
||||
"C and C++ compilers can optimize away information needed to determine a "
|
||||
"function's caller, so it is mistaken for [heap]. You can still tell how "
|
||||
@ -422,7 +427,7 @@ msgstr ""
|
||||
"pochodzenie."
|
||||
|
||||
#. (itstool) path: note/p
|
||||
#: C/faq.page:35
|
||||
#: C/faq.page:38
|
||||
msgid ""
|
||||
"For gcc, the flag <code>-fno-omit-frame-pointer</code> will prevent this "
|
||||
"optimization. The flag is not always needed, for example on x86_64 machines "
|
||||
@ -433,7 +438,7 @@ msgstr ""
|
||||
"komputery w architekturze x86_64 wymagają jej tylko dla optymalizacji -O3."
|
||||
|
||||
#. (itstool) path: note/p
|
||||
#: C/faq.page:41
|
||||
#: C/faq.page:44
|
||||
msgid ""
|
||||
"To get the most detailed and accurate call tree from un-optimized code, use "
|
||||
"these flags: <code>-ggdb -fno-omit-frame-pointer -O0</code>"
|
||||
|
||||
Reference in New Issue
Block a user