/ndk/sources/host-tools/make-3.81/po/ |
make.pot | 82 #: commands.c:422 86 #: commands.c:545 91 #: commands.c:548 96 #: commands.c:561 101 #: commands.c:563 106 #: commands.c:599 107 msgid "# commands to execute" 110 #: commands.c:602 114 #: commands.c:604 196 msgid "Commands were specified for file `%s' at %s:%lu, [all...] |
/external/chromium/chrome/browser/ui/cocoa/toolbar/ |
toolbar_controller.mm | 88 - (void)initCommandStatus:(CommandUpdater*)commands; 162 commands:(CommandUpdater*)commands 167 DCHECK(model && commands && profile && [nibName length]); 171 commands_ = commands; 179 commandObserver_.reset(new CommandObserverBridge(self, commands)); 190 commands:(CommandUpdater*)commands 195 commands:commands [all...] |
/external/chromium/chrome/browser/sessions/ |
session_service.cc | 43 // Identifier for commands written to file. 63 // Every kWritesPerReset commands triggers recreating the file. 426 BuildCommandsFromBrowsers(&(request->commands), 743 request->commands, &(valid_windows.get())); 751 const std::vector<SessionCommand*>& commands, 756 if (CreateTabsAndWindows(commands, &tabs, &windows)) { [all...] |
/external/chromium_org/chrome/browser/sessions/ |
base_session_service.cc | 48 ScopedVector<SessionCommand> commands) { 51 callback.Run(commands.Pass()); 57 ScopedVector<SessionCommand> commands) { 59 callback.Run(commands.Pass()); 62 base::Bind(callback, base::Passed(&commands))); 132 // Backend took ownership of commands.
|
persistent_tab_restore_service.cc | 83 // Identifier for commands written to file. The ordering in the file is as 90 // followed by any number of kCommandUpdateTabNavigation commands (1 per 106 // Number of entries (not commands) before we clobber the file and write 150 // Schedules the commands for a window close. 153 // Schedules the commands for a tab close. |selected_index| gives the index of 179 // Invoked when we've loaded the session commands that identify the previously 182 void OnGotLastSessionCommands(ScopedVector<SessionCommand> commands); 184 // Populates |loaded_entries| with Entries from |commands|. 185 void CreateEntriesFromCommands(const std::vector<SessionCommand*>& commands, 295 // Schedule a command, otherwise if there are no pending commands Save doe [all...] |
/external/chromium_org/gpu/command_buffer/service/ |
cmd_parser_test.cc | 75 // Tests simple commands. 113 // Tests having multiple commands in the buffer. 119 // add 2 commands, test with single ProcessCommand() 147 // add 2 commands again, test with ProcessAllCommands() 178 // add 3 commands with no args (1 word each) 263 // Generates 2 commands.
|
/external/chromium_org/third_party/mesa/src/src/gallium/drivers/svga/include/ |
svga_reg.h | 202 * currently being processed by FIFO commands) will be 567 * Ideally it will do this after some new commands have 613 * process FIFO commands. There is no guarantee as to how many 614 * commands each read will process. 616 * CPU time spent processing FIFO commands will be billed to 631 * any new commands written into the FIFO will be noticed before 639 * just wrote a command or group of commands that it would like 658 * Accel Front -- Front buffer only commands are supported 674 * framebuffer (GFB) and all commands that work only with the GFB. 679 * New 2D commands [all...] |
/external/chromium_org/third_party/openssl/openssl/crypto/engine/ |
engine.h | 131 * control commands on their own. Without this flag, ENGINE_ctrl() handles these 132 * control commands on behalf of the ENGINE using their "cmd_defns" data. */ 137 * commands are called in sequence as part of some stateful process like 174 /* NB: These 3 control commands are deprecated and should not be used. ENGINEs 175 * relying on these commands should compile conditional support for 178 * "discovered" by calling applications. The fact these control commands 203 /* These control commands allow an application to deal with an arbitrary engine 205 * COMMANDS because zero is used to indicate 'end-of-list'. Other commands, 213 * handler need only implement its own commands - the above "meta" commands wil [all...] |
/external/chromium_org/third_party/openssl/openssl/include/openssl/ |
engine.h | 131 * control commands on their own. Without this flag, ENGINE_ctrl() handles these 132 * control commands on behalf of the ENGINE using their "cmd_defns" data. */ 137 * commands are called in sequence as part of some stateful process like 174 /* NB: These 3 control commands are deprecated and should not be used. ENGINEs 175 * relying on these commands should compile conditional support for 178 * "discovered" by calling applications. The fact these control commands 203 /* These control commands allow an application to deal with an arbitrary engine 205 * COMMANDS because zero is used to indicate 'end-of-list'. Other commands, 213 * handler need only implement its own commands - the above "meta" commands wil [all...] |
/external/mesa3d/src/gallium/drivers/svga/include/ |
svga_reg.h | 202 * currently being processed by FIFO commands) will be 567 * Ideally it will do this after some new commands have 613 * process FIFO commands. There is no guarantee as to how many 614 * commands each read will process. 616 * CPU time spent processing FIFO commands will be billed to 631 * any new commands written into the FIFO will be noticed before 639 * just wrote a command or group of commands that it would like 658 * Accel Front -- Front buffer only commands are supported 674 * framebuffer (GFB) and all commands that work only with the GFB. 679 * New 2D commands [all...] |
/external/openssl/crypto/engine/ |
engine.h | 131 * control commands on their own. Without this flag, ENGINE_ctrl() handles these 132 * control commands on behalf of the ENGINE using their "cmd_defns" data. */ 137 * commands are called in sequence as part of some stateful process like 174 /* NB: These 3 control commands are deprecated and should not be used. ENGINEs 175 * relying on these commands should compile conditional support for 178 * "discovered" by calling applications. The fact these control commands 203 /* These control commands allow an application to deal with an arbitrary engine 205 * COMMANDS because zero is used to indicate 'end-of-list'. Other commands, 213 * handler need only implement its own commands - the above "meta" commands wil [all...] |
/external/openssl/include/openssl/ |
engine.h | 131 * control commands on their own. Without this flag, ENGINE_ctrl() handles these 132 * control commands on behalf of the ENGINE using their "cmd_defns" data. */ 137 * commands are called in sequence as part of some stateful process like 174 /* NB: These 3 control commands are deprecated and should not be used. ENGINEs 175 * relying on these commands should compile conditional support for 178 * "discovered" by calling applications. The fact these control commands 203 /* These control commands allow an application to deal with an arbitrary engine 205 * COMMANDS because zero is used to indicate 'end-of-list'. Other commands, 213 * handler need only implement its own commands - the above "meta" commands wil [all...] |
/frameworks/av/services/audioflinger/ |
AudioPolicyService.h | 153 // Thread used for tone playback and to send audio config commands to audio flinger 157 // For audio config commands, it is necessary because audio flinger requires that the calling 163 // commands for tone AudioCommand 255 Vector <AudioCommand *> mAudioCommands; // list of pending commands 258 String8 mName; // string used by wake lock fo delayed commands 342 sp<AudioCommandThread> mAudioCommandThread; // audio commands thread
|
/ndk/sources/host-tools/make-3.81/ |
remake.c | 22 #include "commands.h" 97 We will use the flag below to notice when any commands 98 have actually been run for a target. When no commands 151 later. It will be incremented when any commands are 158 /* Set the goal's `changed' flag if any commands were started 225 any commands were actually started for this goal. */ 273 /* If FILE is not up to date, execute the commands for it. 303 /* This loop runs until we start commands for a double colon rule, or until 430 might get implicit commands that apply to its initial name, only 451 /* If file was specified as a target with no commands, [all...] |
/prebuilts/gcc/darwin-x86/arm/arm-eabi-4.6/share/man/man1/ |
arm-eabi-gdb.1 | 79 commands from the terminal until you tell it to exit with the GDB 122 Here are some of the most frequently needed GDB commands: 261 Execute GDB commands from file \c 279 Do not execute commands from any `\|\c 282 Normally, the commands in these files are executed after all the 304 commands in the command files.
|
arm-eabi-gdbtui.1 | 79 commands from the terminal until you tell it to exit with the GDB 122 Here are some of the most frequently needed GDB commands: 261 Execute GDB commands from file \c 279 Do not execute commands from any `\|\c 282 Normally, the commands in these files are executed after all the 304 commands in the command files.
|
/prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.6/share/man/man1/ |
arm-linux-androideabi-gdb.1 | 79 commands from the terminal until you tell it to exit with the GDB 122 Here are some of the most frequently needed GDB commands: 261 Execute GDB commands from file \c 279 Do not execute commands from any `\|\c 282 Normally, the commands in these files are executed after all the 304 commands in the command files.
|
arm-linux-androideabi-gdbtui.1 | 79 commands from the terminal until you tell it to exit with the GDB 122 Here are some of the most frequently needed GDB commands: 261 Execute GDB commands from file \c 279 Do not execute commands from any `\|\c 282 Normally, the commands in these files are executed after all the 304 commands in the command files.
|
/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/share/man/man1/ |
arm-eabi-gdb.1 | 79 commands from the terminal until you tell it to exit with the GDB 122 Here are some of the most frequently needed GDB commands: 261 Execute GDB commands from file \c 279 Do not execute commands from any `\|\c 282 Normally, the commands in these files are executed after all the 304 commands in the command files.
|
arm-eabi-gdbtui.1 | 79 commands from the terminal until you tell it to exit with the GDB 122 Here are some of the most frequently needed GDB commands: 261 Execute GDB commands from file \c 279 Do not execute commands from any `\|\c 282 Normally, the commands in these files are executed after all the 304 commands in the command files.
|
/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/share/man/man1/ |
arm-linux-androideabi-gdb.1 | 79 commands from the terminal until you tell it to exit with the GDB 122 Here are some of the most frequently needed GDB commands: 261 Execute GDB commands from file \c 279 Do not execute commands from any `\|\c 282 Normally, the commands in these files are executed after all the 304 commands in the command files.
|
arm-linux-androideabi-gdbtui.1 | 79 commands from the terminal until you tell it to exit with the GDB 122 Here are some of the most frequently needed GDB commands: 261 Execute GDB commands from file \c 279 Do not execute commands from any `\|\c 282 Normally, the commands in these files are executed after all the 304 commands in the command files.
|
/external/grub/docs/ |
grub.info | 58 * Commands:: The list of available builtin commands 207 commands. You can also load another configuration file dynamically 209 list of commands (*note Commands::) are a superset of those 214 A menu interface listing preset boot commands, with a programmable 221 is available to edit any preset commands, or write a new boot 225 The list of commands (*note Commands::) are a subset of those 226 supported for configuration files. Editing commands closel [all...] |
/external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/ |
org.eclipse.debug.core_3.6.0.v20100519.jar | |
/external/valgrind/main/coregrind/m_gdbserver/ |
README_DEVELOPERS | 22 gdb does this by sending some commands (e.g. using tcp/ip) to a piece 25 an OS such as GNU/linux) will provide a set of commands allowing gdb 26 to remotely debug the process. Examples of commands are: "get the 28 address yyyyyyyy", etc. The definition of all these commands and the 63 commands from gdb using read system call on a FIFO (e.g. a command 125 How is the Valgrind gdbserver receiving commands/packets from gdb ? 127 The embedded gdbserver reads gdb commands on a named pipe having 131 The embedded gdbserver will reply to gdb commands on a named pipe 136 gdb writes commands on the stdin of vgdb. vgdb reads these 137 commands and writes them on FIFO /tmp/vgdb-pipe-from-vgdb-to-PID-by-USER-on-HOST [all...] |