BosnianUniverseTranslation

Browsing Louisiana French translation

Before translating, be sure to go through Launchpad Translators instructions.

Translating using as a guide.

191.

English:

alloc-then-free

i18n: ectx: property (text), item, widget (QComboBox, keepStacktraces)

Current Louisiana French:

(no translation yet)

Located in tools/memcheck/configpage.ui:141

192.

English:

Freelist maximum size:

i18n: ectx: property (text), widget (QLabel, freelistVolLabel)

Current Louisiana French:

(no translation yet)

Located in tools/memcheck/configpage.ui:154

193.

English:

<html><head/><body>When the client program releases memory using free (in C) or delete (C++), that memory is not immediately made available for re-allocation. Instead, it is marked inaccessible and placed in a queue of freed blocks. The purpose is to defer as long as possible the point at which freed-up memory comes back into circulation. This increases the chance that Memcheck will be able to detect invalid accesses to blocks for some significant period of time after they have been freed.This option specifies the maximum total size, in bytes, of the blocks in the queue. The default value is twenty million bytes. Increasing this increases the total amount of memory used by Memcheck but may detect invalid uses of freed blocks which would otherwise go undetected.</body></html>

i18n: ectx: property (toolTip), widget (QSpinBox, freelistVol)

Current Louisiana French:

(no translation yet)

Located in tools/memcheck/configpage.ui:170

194.

English:

Freelist big-blocks:

i18n: ectx: property (text), widget (QLabel, freelistBigBlocksLabel)

Current Louisiana French:

(no translation yet)

Located in tools/memcheck/configpage.ui:183

195.

English:

<html><head/><body>When making blocks from the queue of freed blocks available for re-allocation, Memcheck will in priority re-circulate the blocks with a size greater or equal to --freelist-big-blocks. This ensures that freeing big blocks (in particular freeing blocks bigger than --freelist-vol) does not immediately lead to a re-circulation of all (or a lot of) the small blocks in the free list. In other words, this option increases the likelihood to discover dangling pointers for the "small" blocks, even when big blocks are freed.Setting a value of 0 means that all the blocks are re-circulated in a FIFO order.</body></html>

i18n: ectx: property (toolTip), widget (QSpinBox, freelistBigBlocks)

Current Louisiana French:

(no translation yet)

Located in tools/memcheck/configpage.ui:196

196.

English:

<html><head/><body>Controls whether Memcheck reports uses of undefined value errors. Set this to no if you don't want to see undefined value errors. It also has the side effect of speeding up Memcheck somewhat.</body></html>

i18n: ectx: property (toolTip), widget (QCheckBox, undefValueErrors)

Current Louisiana French:

(no translation yet)

Located in tools/memcheck/configpage.ui:241

197.

English:

Show undefined values usage

i18n: ectx: property (text), widget (QCheckBox, undefValueErrors)

Current Louisiana French:

(no translation yet)

Located in tools/memcheck/configpage.ui:244

198.

English:

<html><head/><body>When enabled, Memcheck checks that heap blocks are deallocated using a function that matches the allocating function. That is, it expects free to be used to deallocate blocks allocated by malloc, delete for blocks allocated by new, and delete[] for blocks allocated by new[]. If a mismatch is detected, an error is reported. This is in general important because in some environments, freeing with a non-matching function can cause crashes.There is however a scenario where such mismatches cannot be avoided. That is when the user provides implementations of new/new[] that call malloc and of delete/delete[] that call free, and these functions are asymmetrically inlined. For example, imagine that delete[] is inlined but new[] is not. The result is that Memcheck "sees" all delete[] calls as direct calls to free, even when the program source contains no mismatched calls.This causes a lot of confusing and irrelevant error reports. --show-mismatched-frees=no disables these checks. It is not generally advisable to disable them, though, because you may miss real errors as a result.</body></html>

i18n: ectx: property (toolTip), widget (QCheckBox, showMismatchedFrees)

Current Louisiana French:

(no translation yet)

Located in tools/memcheck/configpage.ui:254

199.

English:

Show mismatched frees

i18n: ectx: property (text), widget (QCheckBox, showMismatchedFrees)

Current Louisiana French:

(no translation yet)

Located in tools/memcheck/configpage.ui:257

200.

English:

<html><head/><body>Controls how Memcheck handles 32-, 64-, 128- and 256-bit naturally aligned loads from addresses for which some bytes are addressable and others are not. When yes, such loads do not produce an address error. Instead, loaded bytes originating from illegal addresses are marked as uninitialised, and those corresponding to legal addresses are handled in the normal way.When no, loads from partially invalid addresses are treated the same as loads from completely invalid addresses: an illegal-address error is issued, and the resulting bytes are marked as initialised.Note that code that behaves in this way is in violation of the ISO C/C++ standards, and should be considered broken. If at all possible, such code should be fixed.</body></html>

i18n: ectx: property (toolTip), widget (QCheckBox, partialLoadsOk)

Current Louisiana French:

(no translation yet)

Located in tools/memcheck/configpage.ui:264

This translation is managed by translation group launchpad-translators.

You are not logged in. Please log in to work on translations.

No-one has contributed to this translation yet.