gT,%   " $+ 4P U   " . 1L '~ # , - #% I -f % 9 C \8]C-7/e/7-'GoG3 .:X0g #26:@q7A[,^+"6 C ""(#'#'#> $&K$3r$,$G$*%&F%m%,%!%%'&/&&&'1'6P')')'' ''.(?(!_((&(4((!)#5)Y)(v)))/)1*4*Q*,+%',M,".A."Q.$t.4.U. $/./"E/.h/1/'/#/,0-B0#p00-0%0:1C@1\1]1C?2-2/2/236-3-d3'33G34152E6 x67707 77#8238f878@888A79\y9^<+5A"aAA CE&DlEPF(F'G'6G>^G&G3G,GG%H*mH&HH,H! I-I'I/J&@J gJ1qJ6J)J)K.K >KLK.eKK!KK&K4LRL!hL#LL(LLM/'M1WMM G3ML*U'4)R IC[XHV+?8OJ /g Q&f(=2A"%N61PT,9]- Y<Be0#abD7:>_$Fc;\`K!SdWEZ.5^@"%s": no core file handler recognizes format'%s' is not a recognized file format.(A "base name" is the name of a file with the directory part removed. Example: The base name of "/home/user/hello.c" is "hello.c".) If set, GDB will canonicalize file names (e.g., expand symlinks) before comparing them. Canonicalization is an expensive operation, but it allows the same file be known by more than one base name. If not set (the default), all source files are assumed to have just one base name, and gdb will do file name comparisons more efficiently.Architecture `%s' not recognized. Architecture of file not recognized.Attempt to assign to a value that was optimized out.Can't do read-modify-write to update bitfield; containing word has been optimized outCanceledCanceled the downloadCannot initialize libthread_db: %sCannot initialize thread debugging library: %sCannot instantiate printer for default visualizerCanonicalized file name given to execveCommand object already initialized.Could not evaluate visualizer expression: %sCould not locate initialization function: %s.Could not recognize DWARF regnum %dCouldn't initialize WINSOCK.Couldn't recognize %s registers in core file.Couldn't recognize signal trampoline.Debugger's behavior regarding pending breakpoints is %s. Disabling randomization of debuggee's virtual address space is %s. Disabling randomization of debuggee's virtual address space is unsupported on this platform.Disabling randomization of debuggee's virtual address space is unsupported on this platform. Enable or disable an optimization trusting PAD types over XVS typesEnabled packet %s (%s) not recognized by stubError disabling address space randomization: %sError restoring address space randomization: %sEvent type not recognized. Explicitly sized type can not contain non-bitfield "%s"Failed to initialize (didn't receive packet).Failed to initialize new interp "%s" %sFailed to initialize.GDB bug: target.c (gdb_signal_from_host): unrecognized real-time signalGDB can sometimes determine the values of function arguments at entry, in addition to their current values. This option tells GDB whether to print the current value, the value at entry (marked as val@entry), or both. Note that one or both of these values may be .If on, an unrecognized breakpoint location will cause gdb to create a pending breakpoint. If off, an unrecognized breakpoint location results in an error. If auto, an unrecognized breakpoint location results in a user-query to see if a pending breakpoint should be created.Implicitly sized type can not contain bitfield "%s"Initialize a convenience variable if necessary. init-if-undefined VARIABLE = EXPRESSION Set an internal VARIABLE to the result of the EXPRESSION if it does not exist or does not contain a value. The EXPRESSION is not evaluated if the VARIABLE is already initialized.Interpreter `%s' unrecognizedMissing nul SOOperator `%c' not recognized on expression `%s'.Optimized outRegister %d was optimized outReinitialize source path to empty? Remote board reset, debug protocol re-initialized.Section index is uninitializedSet debugger's behavior regarding pending breakpoints.Set disabling of debuggee's virtual address space randomization.Show debugger's behavior regarding pending breakpoints.Show disabling of debuggee's virtual address space randomization.Specify how to handle a signal. Args are signals and actions to apply to those signals. Symbolic signals (e.g. SIGSEGV) are recommended but numeric signals from 1-15 are allowed for compatibility with old versions of GDB. Numeric ranges may be specified with the form LOW-HIGH (e.g. 1-5). The special arg "all" is recognized to mean all signals except those used by the debugger, typically SIGTRAP and SIGINT. Recognized actions include "s" (toggles between stop and nostop), "r" (toggles between print and noprint), "i" (toggles between pass and nopass), "Q" (noprint) Stop means reenter debugger if this signal happens (implies print). Print means print a message if this signal happens. Pass means let program see this signal; otherwise program doesn't know. Ignore is a synonym for nopass and noignore is a synonym for pass. Pass and Stop may be combined.Specify how to handle signals. Usage: handle SIGNAL [ACTIONS] Args are signals and actions to apply to those signals. If no actions are specified, the current settings for the specified signals will be displayed instead. Symbolic signals (e.g. SIGSEGV) are recommended but numeric signals from 1-15 are allowed for compatibility with old versions of GDB. Numeric ranges may be specified with the form LOW-HIGH (e.g. 1-5). The special arg "all" is recognized to mean all signals except those used by the debugger, typically SIGTRAP and SIGINT. Recognized actions include "stop", "nostop", "print", "noprint", "pass", "nopass", "ignore", or "noignore". Stop means reenter debugger if this signal happens (implies print). Print means print a message if this signal happens. Pass means let program see this signal; otherwise program doesn't know. Ignore is a synonym for nopass and noignore is a synonym for pass. Pass and Stop may be combined. Multiple signals may be specified. Signal numbers and signal names may be interspersed with actions, with the actions being performed for all signals cumulatively specified.Storage class %d not recognized during scanTemplate argument is optimized outThe program being debugged entered a std::terminate call, most likely caused by an unhandled C++ exception. GDB blocked this call in order to prevent the program from being terminated, and has restored the context to its original state before the call. To change this behaviour use "set unwind-on-terminating-exception off". Evaluation of the expression containing the function (%s) will be abandoned.The program being debugged was signaled while in a function called from GDB. GDB has restored the context to what it was before the call. To change this behavior use "set unwindonsignal off". Evaluation of the expression containing the function (%s) will be abandoned.The program being debugged was signaled while in a function called from GDB. GDB remains in the frame where the signal was received. To change this behavior use "set unwindonsignal on". Evaluation of the expression containing the function (%s) will be abandoned. When the function is done executing, GDB will silently stop.This is the maximum number of characters GDB will ignore when trying to synchronize with the remote system. A value of -1 means that there is no limit. (Note that these characters are printed out even though they are ignored.)Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code.Unrecognized %d-bit floating-point type.Unrecognized DWARF opcode 0x%02x at %ldUnrecognized breakpoint/watchpoint typeUnrecognized char '%c' in tracepoint definition, skipping restUnrecognized cross-reference type `%c'Unrecognized escape character \%c in format string.Unrecognized format specifier '%c' in printfUnrecognized option '%s' to info macro command. Try "help info macro".Unrecognized or ambiguous flag word: "%s".Unrecognized range check setting: "%s"Unrecognized storage class %d.Unrecognized tracepoint piece '%c', ignoringUnrecognized watch register styleWhen this mode is on (which is the default), randomization of the virtual address space is disabled. Standalone programs run with the randomization enabled by default on some platforms.`%s' has been optimized out, cannot use`%s' is optimized away and cannot be collected.auto-load: And canonicalized as "%s". canceledfield %s is nonexistent or has been optimized outinternal error: string "%s" failed to be canonicalizedmips_register_to_value: unrecognized casemips_value_to_register: unrecognized casemissing nul SOoptimized outport 0x%04x, behavior: print_bp_stop_message: unrecognized enum valuesect_index_data not initializedsect_index_rodata not initializedsect_index_text not initializedstatic field %s has been optimized outstatic field `%s' has been optimized out, cannot usetoo many initializersunrecognized .gcc_compiled_longXXunrecognized DW_MACFINO opcode 0x%xunrecognized attribute: `%s'unrecognized bitness `%c' for probe `%s'unrecognized character typeunrecognized flag '%c'unrecognized item "%s" in "qSupported" responseunrecognized version `%d' in .debug_macro sectionvalue has been optimized outProject-Id-Version: crash Report-Msgid-Bugs-To: FULL NAME PO-Revision-Date: 2020-04-10 21:55+0000 Last-Translator: Anthony Harrington Language-Team: English (United Kingdom) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Launchpad-Export-Date: 2024-09-02 19:38+0000 X-Generator: Launchpad (build 1b1ed1ad2dbfc71ee62b5c5491c975135a771bf0) "%s": no core file handler recognises format'%s' is not a recognised file format.(A "base name" is the name of a file with the directory part removed. Example: The base name of "/home/user/hello.c" is "hello.c".) If set, GDB will canonicalise file names (e.g., expand symlinks) before comparing them. Canonicalisation is an expensive operation, but it allows the same file be known by more than one base name. If not set (the default), all source files are assumed to have just one base name, and gdb will do file name comparisons more efficiently.Architecture `%s' not recognised. Architecture of file not recognised.Attempt to assign to a value that was optimised out.Can't do read-modify-write to update bitfield; containing word has been optimised outCancelledCancelled the downloadCannot initialise libthread_db: %sCannot initialise thread debugging library: %sCannot instantiate printer for default visualiserCanonicalised file name given to execveCommand object already initialised.Could not evaluate visualiser expression: %sCould not locate initialisation function: %s.Could not recognise DWARF regnum %dCouldn't initialise WINSOCK.Couldn't recognise %s registers in core file.Couldn't recognise signal trampoline.Debugger's behaviour regarding pending breakpoints is %s. Disabling randomisation of debuggee's virtual address space is %s. Disabling randomisation of debuggee's virtual address space is unsupported on this platform.Disabling randomisation of debuggee's virtual address space is unsupported on this platform. Enable or disable an optimisation trusting PAD types over XVS typesEnabled packet %s (%s) not recognised by stubError disabling address space randomisation: %sError restoring address space randomisation: %sEvent type not recognised. Explicitly sized type cannot contain non-bitfield "%s"Failed to initialise (didn't receive packet).Failed to initialise new interp "%s" %sFailed to initialise.GDB bug: target.c (gdb_signal_from_host): unrecognised real-time signalGDB can sometimes determine the values of function arguments at entry, in addition to their current values. This option tells GDB whether to print the current value, the value at entry (marked as val@entry), or both. Note that one or both of these values may be .If on, an unrecognised breakpoint location will cause gdb to create a pending breakpoint. If off, an unrecognised breakpoint location results in an error. If auto, an unrecognised breakpoint location results in a user-query to see if a pending breakpoint should be created.Implicitly sized type cannot contain bitfield "%s"Initialise a convenience variable if necessary. init-if-undefined VARIABLE = EXPRESSION Set an internal VARIABLE to the result of the EXPRESSION if it does not exist or does not contain a value. The EXPRESSION is not evaluated if the VARIABLE is already initialised.Interpreter `%s' unrecognisedMissing null SOOperator `%c' not recognised on expression `%s'.Optimised outRegister %d was optimised outReinitialise source path to empty? Remote board reset, debug protocol re-initialised.Section index is uninitialisedSet debugger's behaviour regarding pending breakpoints.Set disabling of debuggee's virtual address space randomisation.Show debugger's behaviour regarding pending breakpoints.Show disabling of debuggee's virtual address space randomisation.Specify how to handle a signal. Args are signals and actions to apply to those signals. Symbolic signals (e.g. SIGSEGV) are recommended but numeric signals from 1-15 are allowed for compatibility with old versions of GDB. Numeric ranges may be specified with the form LOW-HIGH (e.g. 1-5). The special arg "all" is recognised to mean all signals except those used by the debugger, typically SIGTRAP and SIGINT. Recognised actions include "s" (toggles between stop and nostop), "r" (toggles between print and noprint), "i" (toggles between pass and nopass), "Q" (noprint) Stop means re-enter debugger if this signal happens (implies print). Print means print a message if this signal happens. Pass means let program see this signal; otherwise program doesn't know. Ignore is a synonym for nopass and noignore is a synonym for pass. Pass and Stop may be combined.Specify how to handle signals. Usage: handle SIGNAL [ACTIONS] Args are signals and actions to apply to those signals. If no actions are specified, the current settings for the specified signals will be displayed instead. Symbolic signals (e.g. SIGSEGV) are recommended but numeric signals from 1-15 are allowed for compatibility with old versions of GDB. Numeric ranges may be specified with the form LOW-HIGH (e.g. 1-5). The special arg "all" is recognised to mean all signals except those used by the debugger, typically SIGTRAP and SIGINT. Recognised actions include "stop", "nostop", "print", "noprint", "pass", "nopass", "ignore", or "noignore". Stop means reenter debugger if this signal happens (implies print). Print means print a message if this signal happens. Pass means let program see this signal; otherwise program doesn't know. Ignore is a synonym for nopass and noignore is a synonym for pass. Pass and Stop may be combined. Multiple signals may be specified. Signal numbers and signal names may be interspersed with actions, with the actions being performed for all signals cumulatively specified.Storage class %d not recognised during scanTemplate argument is optimised outThe program being debugged entered a std::terminate call, most likely caused by an unhandled C++ exception. GDB blocked this call in order to prevent the program from being terminated, and has restored the context to its original state before the call. To change this behaviour, use "set unwind-on-terminating-exception off". Evaluation of the expression containing the function (%s) will be abandoned.The program being debugged was signaled while in a function called from GDB. GDB has restored the context to what it was before the call. To change this behaviour use "set unwindonsignal off". Evaluation of the expression containing the function (%s) will be abandoned.The program being debugged was signalled while in a function called from GDB. GDB remains in the frame where the signal was received. To change this behaviour use "set unwindonsignal on". Evaluation of the expression containing the function (%s) will be abandoned. When the function is done executing, GDB will silently stop.This is the maximum number of characters GDB will ignore when trying to synchronise with the remote system. A value of -1 means that there is no limit. (Note that these characters are printed out even though they are ignored.)Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initialisers and track explicitly loaded dynamic code.Unrecognised %d-bit floating-point type.Unrecognised DWARF opcode 0x%02x at %ldUnrecognised breakpoint/watchpoint typeUnrecognised char '%c' in tracepoint definition, skipping restUnrecognised cross-reference type `%c'Unrecognised escape character \%c in format string.Unrecognised format specifier '%c' in printfUnrecognised option '%s' to info macro command. Try "help info macro".Unrecognised or ambiguous flag word: "%s".Unrecognised range check setting: "%s"Unrecognised storage class %d.Unrecognised tracepoint piece '%c', ignoringUnrecognised watch register styleWhen this mode is on (which is the default), randomisation of the virtual address space is disabled. Standalone programs run with the randomisation enabled by default on some platforms.`%s' has been optimised out, cannot use`%s' is optimised away and cannot be collected.auto-load: And canonicalised as "%s". cancelledfield %s is nonexistent or has been optimised outinternal error: string "%s" failed to be canonicalisedmips_register_to_value: unrecognised casemips_value_to_register: unrecognised casemissing null SOoptimised outport 0x%04x, behaviour: print_bp_stop_message: unrecognised enum valuesect_index_data not initialisedsect_index_rodata not initialisedsect_index_text not initialisedstatic field %s has been optimised outstatic field `%s' has been optimised out, cannot usetoo many initialisersunrecognised .gcc_compiled_longXXunrecognised DW_MACFINO opcode 0x%xunrecognised attribute: `%s'unrecognised bitness `%c' for probe `%s'unrecognised character typeunrecognised flag '%c'unrecognised item "%s" in "qSupported" responseunrecognised version `%d' in .debug_macro sectionvalue has been optimised out