| /external/elfutils/ |
| D | NEWS | 386 Improved SHT_GROUP sections handling.
406 libdw: Fix for handling huge .debug_aranges section.
408 libdwfl: Fix for handling prelinked DSO with separate debug file.
430 libdwfl: Fixes in core-file handling, support cores from PIEs.
437 libdw: Fixes in CFI handling, best possible handling of bogus CFA ops.
475 Location expression handling now supports DW_OP_implicit_value.
494 Basic handling of some new encodings slated for DWARF 4.
520 readelf: Implement call frame information and exception handling dumping.
540 nm: bug fixes for handling corrupt input files
555 strip: changed handling of ET_REL files wrt symbol tables and relocs
[all …]
|
| /external/nist-sip/java/gov/nist/javax/sip/header/ |
| D | ContentDisposition.java | 106 public void setHandling(String handling) throws ParseException { in setHandling() argument
107 if (handling == null) in setHandling()
111 this.setParameter("handling", handling); in setHandling()
|
| /external/llvm/docs/ |
| D | ExceptionHandling.rst | 12 exception handling in LLVM. It describes the format that LLVM exception
13 handling information takes, which is useful for those interested in creating
15 provides specific examples of what exception handling information is used for in
21 Exception handling for most programming languages is designed to recover from
23 exception handling should not interfere with the main flow of an application's
29 speculative exception handling code in the flow of an application's main
33 A more complete description of the Itanium ABI exception handling runtime
46 Setjmp/Longjmp (SJLJ) based exception handling uses LLVM intrinsics
48 exception handling.
60 In contrast to DWARF exception handling, which encodes exception regions and
[all …]
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | ExceptionHandling.rst | 12 exception handling in LLVM. It describes the format that LLVM exception
13 handling information takes, which is useful for those interested in creating
15 provides specific examples of what exception handling information is used for in
21 Exception handling for most programming languages is designed to recover from
23 exception handling should not interfere with the main flow of an application's
29 speculative exception handling code in the flow of an application's main
33 A more complete description of the Itanium ABI exception handling runtime
46 Setjmp/Longjmp (SJLJ) based exception handling uses LLVM intrinsics
48 exception handling.
60 In contrast to DWARF exception handling, which encodes exception regions and
[all …]
|
| /external/clang/test/Analysis/ |
| D | misc-ps-region-store.mm | 6 // This files tests our path-sensitive handling of Objective-c++ files.
9 // Test basic handling of references.
20 // Test basic handling of references with Objective-C classes.
|
| /external/python/oauth2client/ |
| D | CHANGELOG.md | 143 * Fix (more like clarify) `bytes` / `str` handling in crypto
180 * `tox` updates for new environment handling in `tox`.
189 * Better handling of `body` during token refresh when `body` is a stream.
190 * Better handling of expired tokens in storage.
200 * Better handling of filesystem errors in credential refresh.
258 * Quick bugfix for bad error handling in from_json.
269 * Better exception handling around missing crypto libraries (#56).
275 * Better unicode handling with PKCS12 passwords (#31, thanks @jterrace).
276 * Better retry handling with bad server replies on refresh (#29, thanks
329 * Consolidate handling of scopes.
[all …]
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/X86/ |
| D | implicit-null-check.ll | 329 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 5
331 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 7
333 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 9
335 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 7
337 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 3
339 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 4
341 ; OBJDUMP-NEXT: Fault kind: FaultingStore, faulting PC offset: 0, handling PC offset: 7
343 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 11
|
| /external/ltp/testcases/network/stress/dns/ |
| D | 00_Descriptions.txt | 2 Verify the dns server or the kernel is not down after handling
6 Verify the dns server or the kernel is not down after handling
|
| /external/catch2/projects/ExtraTests/ |
| D | ToDo.txt | 5 CATCH_CONFIG_WINDOWS_SEH // Enable SEH handling on Windows
8 CATCH_CONFIG_POSIX_SIGNALS // Enable handling POSIX signals
|
| /external/python/cpython3/Doc/c-api/ |
| D | codec.rst | 23 *encoding* using the error handling method defined by *errors*. *errors* may
32 *encoding* using the error handling method defined by *errors*. *errors* may
75 Register the error handling callback function *error* under the given *name*.
94 Lookup the error handling callback function registered under *name*. As a
95 special case *NULL* can be passed, in which case the error handling callback
|
| /external/python/cpython2/Doc/c-api/ |
| D | codec.rst | 23 *encoding* using the error handling method defined by *errors*. *errors* may
32 *encoding* using the error handling method defined by *errors*. *errors* may
75 Register the error handling callback function *error* under the given *name*.
94 Lookup the error handling callback function registered under *name*. As a
95 special case *NULL* can be passed, in which case the error handling callback
|
| /external/autotest/client/site_tests/network_DhcpFailureWithStaticIP/ |
| D | control | 14 Note that shill's DHCP timeout handling depends on the device technology.
15 This test only vaidates shill's handling of DHCP timeouts for Ethernet.
|
| /external/autotest/client/site_tests/network_DhcpNegotiationTimeout/ |
| D | control | 15 Note that shill's DHCP timeout handling depends on the device technology.
16 This test only vaidates shill's handling of DHCP timeouts for Ethernet.
|
| /external/python/cpython2/Misc/NEWS.d/ |
| D | 2.7rc2.rst | 16 Previous change to ``sys.argv[0]`` handling for -m command line option
17 reverted due to unintended side effects on handling of ``sys.path``. See
96 logging: Improved error handling for Unicode in exception text.
|
| /external/pdfium/third_party/lcms/ |
| D | 0026-more-unsupported-characters.patch | 10 - // the cach<E9> that with the pixel handling
12 + // the cache that with the pixel handling
42 - // the cach<E9> that with the pixel handling
44 + // the cache that with the pixel handling
|
| /external/mockftpserver/tags/2.x_Before_IDEA/src/main/groovy/org/mockftpserver/fake/command/ |
| D | AbstractFakeCommandHandler.groovy | 59 LOG.warn("Error handling command: $command; ${e}")
63 LOG.warn("Error handling command: $command; ${e}")
67 LOG.warn("Error handling command: $command; ${e}")
71 LOG.warn("Error handling command: $command; ${e}; path: ${e.path}")
75 LOG.warn("Error handling command: $command; ${e}; path: ${e.path}")
80 LOG.warn("Error handling command: $command; ${e}")
|
| /external/libxml2/ |
| D | TODO | 87 - problem: do we want to keep and maintain the code for handling
127 => defaulted attributes handling
140 - HTML: handling of Script and style data elements, need special code in
141 the parser and saving functions (handling of < > " ' ...):
178 - checking/handling of newline normalization
182 - checking/handling of xml:space
184 - handling done, not well tested
270 - Better error handling, use a dedicated, overridable error
271 handling function.
|
| D | NEWS | 89 Fix handling of mmap errors (Daniel Veillard),
219 Improve handling of xmlStopParser() (Daniel Veillard),
328 Enforce XML_PARSER_EOF state handling through the parser (Daniel Veillard),
418 URI handling code is not OOM resilient (Daniel Veillard),
580 Fix handling of XML-1.0 XML namespace declaration (Daniel Veillard),
582 Fix handling of apos in URIs (Daniel Veillard),
594 Various cleanups on encoding handling (Daniel Veillard),
770 564217 fix structured error handling problems,
840 (Volker Grabsch), handling of entity push errors (Ashwin), fix a slowdown
844 serious cleanup of the entity handling code
[all …]
|
| /external/python/cpython2/Doc/library/ |
| D | autogil.rst | 2 :mod:`autoGIL` --- Global Interpreter Lock handling in event loops
7 :synopsis: Global Interpreter Lock handling in event loops.
|
| D | codecs.rst | 22 manages the codec and error handling lookup process.
31 *Errors* may be given to set the desired error handling scheme. The
35 information on codec error handling.
44 *Errors* may be given to set the desired error handling scheme. The
48 information on codec error handling.
108 as well as any other error handling name defined via :func:`register_error`.
182 Register the error handling function *error_handler* under the name *name*.
209 Implements the ``strict`` error handling: each encoding or decoding error
215 Implements the ``replace`` error handling: malformed data is replaced with a
222 Implements the ``ignore`` error handling: malformed data is ignored and
[all …]
|
| /external/linux-kselftest/tools/testing/selftests/tc-testing/ |
| D | TODO.txt | 23 - Proper exception handling - make an exception class and use it
25 - a TestCase class, for easier testcase handling, searching, comparison
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Analysis/ConstantFolding/ |
| D | cast-vector.ll | 7 ; llvm::ConstantFoldCastInstruction when handling ptrtoint.
22 ; llvm::ConstantFoldCastInstruction when handling ptrtoint.
|
| /external/llvm/test/CodeGen/X86/ |
| D | implicit-null-check.ll | 221 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 5
223 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 7
225 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 7
227 ; OBJDUMP-NEXT: Fault kind: FaultingLoad, faulting PC offset: 0, handling PC offset: 3
|
| /external/python/cpython3/Doc/library/ |
| D | codecs.rst | 25 manages the codec and error handling lookup process. Most standard codecs
40 *Errors* may be given to set the desired error handling scheme. The
44 information on codec error handling.
50 *Errors* may be given to set the desired error handling scheme. The
54 information on codec error handling.
194 *errors* may be given to define the error handling. It defaults to ``'strict'``
215 *errors* may be given to define the error handling. It defaults to
293 To simplify and standardize error handling,
294 codecs may implement different error handling schemes by
382 Register the error handling function *error_handler* under the name *name*.
[all …]
|
| /external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/WebAssembly/ |
| D | WebAssembly.td | 41 SubtargetFeature<"exception-handling", "HasExceptionHandling", "true",
42 "Enable Wasm exception handling">;
|