summaryrefslogtreecommitdiffstats
path: root/ipc
Commit message (Collapse)AuthorAgeFilesLines
* Remove an IPC::ChannelProxy constructor that is not actually implemented ↵bryner@chromium.org2012-06-191-6/+0
| | | | | | | | anywhere. Review URL: https://chromiumcodereview.appspot.com/10577006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143007 0039d316-1c4b-4281-b951-d872f2087c98
* Add untrusted NaCl build for PPAPI proxy.bbudge@chromium.org2012-06-162-8/+5
| | | | | | | | | | This patch refactors ppapi_shared.gypi and ppapi_proxy.gypi into proper includes, adds ppapi_shared_untrusted and ppapi_proxy_untrusted .gyp files, and integrates them into the nacl_irt build (ppapi/native_client/native_client.gyp). In order to build without link errors, it includes our plugin side initialization of PluginDispatcher, and a PpapiPluginMain definition. When the 'build_ppapi_ipc_proxy_untrusted' gyp flag is set to '1', this will build a working NaCl IRT using the Chrome IPC proxy. BUG=116317 TEST=compiles, runs HelloWorld and GetURL SDK examples. Review URL: https://chromiumcodereview.appspot.com/10565015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142540 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 142482 - Add untrusted NaCl build for PPAPI proxy.bbudge@chromium.org2012-06-152-5/+8
| | | | | | | | | | | | | This patch refactors ppapi_shared.gypi and ppapi_proxy.gypi into proper includes, adds ppapi_shared_untrusted and ppapi_proxy_untrusted .gyp files, and integrates them into the nacl_irt build (ppapi/native_client/native_client.gyp). In order to build without link errors, it includes our plugin side initialization of PluginDispatcher, and a PpapiPluginMain definition. When the 'build_ppapi_ipc_proxy_untrusted' gyp flag is set to '1', this will build a working NaCl IRT using the Chrome IPC proxy. BUG=116317 TEST=compiles, runs HelloWorld and GetURL SDK examples. Review URL: https://chromiumcodereview.appspot.com/10546140 TBR=bbudge@chromium.org Review URL: https://chromiumcodereview.appspot.com/10565012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142494 0039d316-1c4b-4281-b951-d872f2087c98
* Add untrusted NaCl build for PPAPI proxy.bbudge@chromium.org2012-06-152-8/+5
| | | | | | | | | | This patch refactors ppapi_shared.gypi and ppapi_proxy.gypi into proper includes, adds ppapi_shared_untrusted and ppapi_proxy_untrusted .gyp files, and integrates them into the nacl_irt build (ppapi/native_client/native_client.gyp). In order to build without link errors, it includes our plugin side initialization of PluginDispatcher, and a PpapiPluginMain definition. When the 'build_ppapi_ipc_proxy_untrusted' gyp flag is set to '1', this will build a working NaCl IRT using the Chrome IPC proxy. BUG=116317 TEST=compiles, runs HelloWorld and GetURL SDK examples. Review URL: https://chromiumcodereview.appspot.com/10546140 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142482 0039d316-1c4b-4281-b951-d872f2087c98
* Add an untrusted NaCl build for IPC.bbudge@chromium.org2012-06-133-69/+90
| | | | | | | | | BUG=116317 TEST=compiles Review URL: https://chromiumcodereview.appspot.com/10534115 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141834 0039d316-1c4b-4281-b951-d872f2087c98
* Separate out IPC::Message::Sender and Channel::Listener into a separate class.brettw@chromium.org2012-06-1116-70/+131
| | | | | | | | | | | | | I fixed the places that did IPC::Channel::Sender (I don't even know how this compiled, but I presume this means the "Sender" base class of the "Channel" which ends up being right). We can fix the other users of this later. BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10541065 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141534 0039d316-1c4b-4281-b951-d872f2087c98
* Add dmichael to ipc OWNERS for NaCl-related code.dmichael@chromium.org2012-06-111-0/+3
| | | | | | | | | | BUG=116317 TEST= R=jam@chromium.org Review URL: https://chromiumcodereview.appspot.com/10532094 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141461 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI/NaCl: Fix double-delete in ipc_channel_nacldmichael@chromium.org2012-06-111-2/+2
| | | | | | | | | | | BUG=116317 TEST= R=bbudge Review URL: https://chromiumcodereview.appspot.com/10545101 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141435 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI/NaCl: Make ipc_channel_nacl process incoming messages.dmichael@chromium.org2012-06-061-0/+6
| | | | | | | | | | | | | On NaCl, we don't have libevent to tell us when there are bytes to be read. Instead, we use a reader thread that does a blocking read and posts data back to DidRecvMsg on the channel's main thread. Since this is how we know there's data to read, we must call ProcessIncomingMessages(). R=bbudge BUG=116317 TEST= Review URL: https://chromiumcodereview.appspot.com/10537031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140848 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI/NaCl: Minor fixes to ipc_channel_nacldmichael@chromium.org2012-06-061-1/+2
| | | | | | | | | | | | | 1) Make ReaderThreadRunner keep a reference to the main message loop proxy (this probably doesn't matter in practice). 2) Add missing return statement to ChannelImpl::Connect. R=bbudge BUG=116317 TEST= Review URL: https://chromiumcodereview.appspot.com/10534024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140791 0039d316-1c4b-4281-b951-d872f2087c98
* Fixing gcc 4.7 building problems.shenhan@google.com2012-06-053-3/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | a) - gcc-4.7 improved the implicit headers that it includes. with <4.7, the gthr-default.h file always pulls in unistd.h. with >=4.7, they avoided that include when possible. so code that isn't including unistd.h itself but needs it now breaks. b) - narrowing conversion in initiliazation list now raises an 'ill-formed conversion' warning, which causes error when -Werror is given. [THIS PART IS NOW REVERTED IN THE PATCH} c) - included patches from pastebin - http://pastebin.com/raw.php?i=p3UKs7Cg Note - this may not be fixing all the gcc 4.7 build problems for all parts, but rather than submitting one big-fix-for-all CL, we'd better do it incrementally (given that all the modification is reasonable and minor) so that at least some parts get a successful gcc 4.7 build. BUG=None TEST=Built successfully using GCC-4.7 under chromium chroot Review URL: https://chromiumcodereview.appspot.com/10451068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140470 0039d316-1c4b-4281-b951-d872f2087c98
* This groups the ParamTraits into different categories and orders the .cc ↵brettw@chromium.org2012-06-042-507/+587
| | | | | | | | | | | file the same. It makes all non-trivial Read/Write calls non-inline. TEST=it compiles BUG=none Review URL: https://chromiumcodereview.appspot.com/10498002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140375 0039d316-1c4b-4281-b951-d872f2087c98
* Remove some obscure unused Windows types from the ParamTraits specializations.brettw@chromium.org2012-06-021-84/+0
| | | | | | | | | | TEST=it compiles BUG=none Review URL: https://chromiumcodereview.appspot.com/10485002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140138 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI/NaCl: Re-land speculative implementation for ipc_channel_nacl.ccdmichael@chromium.org2012-05-314-86/+334
| | | | | | | | | | | | | Original CL: http://codereview.chromium.org/10174048/ Was committed at 139635, reverted at 139646 due to a flake. BUG=116317 TEST= TBR=dmichael@chromium.org Review URL: https://chromiumcodereview.appspot.com/10442112 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139840 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 139635 - PPAPI/NaCl: Speculative implementation for ipc_channel_nacl.ccrch@chromium.org2012-05-304-334/+86
| | | | | | | | | | | | | BUG=116317 TEST= Review URL: https://chromiumcodereview.appspot.com/10174048 TBR=dmichael@chromium.org Review URL: https://chromiumcodereview.appspot.com/10456039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139646 0039d316-1c4b-4281-b951-d872f2087c98
* Move ParamTraits<base::PlatformFileInfo> and <base::PlatformFileError>.tsepez@chromium.org2012-05-302-0/+57
| | | | | | | | | | Move thse to ipc/ from content/common so that they may be used in directories parallel to content/. Pre-requisite for fixing the associated bug. BUG=127624 Review URL: https://chromiumcodereview.appspot.com/10442072 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139636 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI/NaCl: Speculative implementation for ipc_channel_nacl.ccdmichael@chromium.org2012-05-304-86/+334
| | | | | | | | | | BUG=116317 TEST= Review URL: https://chromiumcodereview.appspot.com/10174048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139635 0039d316-1c4b-4281-b951-d872f2087c98
* Fix ninja build for android.yfriedman@chromium.org2012-05-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The primary issues is specifying the right path to PRODUCT_DIR (i.e. out/Release). The gyp generator for make specifies the absolute path but for ninja would use a relative path. Since the gyp targets don't line up with where the ant build files are located this causes failures such as base's java being generated in base/android/out/Release/... See: https://groups.google.com/forum/#!msg/gyp-developer/K2T_9obUya0/qq78_Ut-E-AJ for details. A couple of other minor fixes: - content java files are placed in out/Release/java/content to be consisent with other packages. - shared-libraries are now referenced by correct variables for apk-based tests - removed unused media/base/android/java/java.gyp (target is in media/media.gyp) TBR=mark@chromium.org,ben@chromium.org,rsleevi@chromium.org Review URL: https://chromiumcodereview.appspot.com/10386188 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139418 0039d316-1c4b-4281-b951-d872f2087c98
* Add APK targets for content_unittests and net_unittests.nileshagrawal@chromium.org2012-05-251-33/+10
| | | | | | | | | | | | | | - Add a gyp template to simplify adding new targets. - Add support for multiple jars in the test APK. BUG=125059 TEST= Review URL: https://chromiumcodereview.appspot.com/10399126 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139106 0039d316-1c4b-4281-b951-d872f2087c98
* Android: Get the cache directory using path service.nileshagrawal@chromium.org2012-05-251-22/+28
| | | | | | | | | | | | | | "/data/local" is not writable on non-rooted devices and while running tests in an APK. BUG=125059 TEST= Review URL: https://chromiumcodereview.appspot.com/10443021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138981 0039d316-1c4b-4281-b951-d872f2087c98
* Disable IPCChannelTest.SendMessageInChannelConnected on Windows for being ↵danakj@chromium.org2012-05-241-1/+7
| | | | | | | | | | | | flakey. BUG=129595 TEST= TBR=jeremy@chromium.org Review URL: https://chromiumcodereview.appspot.com/10440023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138834 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI/NaCl: Fix leaky NaClIPCAdapter test.dmichael@chromium.org2012-05-162-2/+4
| | | | | | | | | | | | The NaClIPCAdapter was not leaking, but the Channel deletion is posted as a task that the test was not running. This makes all the NaClIPCAdapter test cases do RunAllPending on shutdown to delete stuff. Unfortunately, one of the tests results in calling "Close()" on the channel in one of these tasks, and that fails for IPC::TestSink, because IPC::Channel::Close dereferences channel_impl_ unconditionally, and the channel_impl_ is NULL for TestSink. So this patch also makes Channel::Close() do nothing if channel_impl_ is NULL. BUG=127954 TEST= Review URL: https://chromiumcodereview.appspot.com/10383167 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@137471 0039d316-1c4b-4281-b951-d872f2087c98
* Run APK tests on the android_test trybot.nileshagrawal@chromium.org2012-05-161-1/+2
| | | | | | | | | | | | Test failures are ignored for now. TBR=mark@chromium.org,tsepez@chromium.org BUG=125059 TEST= Review URL: https://chromiumcodereview.appspot.com/10387086 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@137352 0039d316-1c4b-4281-b951-d872f2087c98
* Change the way _EXPORT macros look.thakis@chromium.org2012-05-151-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With the current setup, if you have a header file my_class.h class BASE_EXPORT MyClass { public: void MyInlineMethod() { /* do stuff, inline */ } }; then every cc file that includes my_class.h will have a public symbol for MyInlineMethod (because inline methods need to be emitted to every translation unit, and the linker sorts them out). With the components build, the linker can't decide to drop these inline methods, so every .so that uses this header file will have the same public symbol. With this proposed change, the symbol will only be visible in the target the header file belongs to, and it will be hidden in all other components. That's cleaner, and it also prevents accident hidden dependencies (say target A depends on B, and B depends on C. A accidentally uses an inline function from a class in C. With this change, that would result in a linker error, and an explicit dependency from A on C would have to be added). Also add a missing CHROMEOS_IMPLEMENTATION define which went unnoticed until now. BUG=90078 TEST=Things still build. TBR=ben, tony, viettrungluu, thestig, agl, willchan Review URL: https://chromiumcodereview.appspot.com/10386108 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@137130 0039d316-1c4b-4281-b951-d872f2087c98
* Log message class/line in IPC::ChannelProxy::Context::OnDispatchMessagepiman@chromium.org2012-05-111-2/+4
| | | | | | | | | | BUG=none TEST=about:tracing Review URL: https://chromiumcodereview.appspot.com/10380046 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136703 0039d316-1c4b-4281-b951-d872f2087c98
* Fix chromium_base.jar path for APK builds.nileshagrawal@chromium.org2012-05-111-2/+2
| | | | | | | | | | | | | Also, Don't make try_compile_test bot RED if native tests APK fails to compile. BUG=125059 TBR=mark@chromium.org,tsepez@chromium.org TEST= Review URL: https://chromiumcodereview.appspot.com/10310098 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136496 0039d316-1c4b-4281-b951-d872f2087c98
* Fix ipc_channel_win logging for failed pipe creation.bryner@chromium.org2012-05-061-1/+1
| | | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/10378022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@135607 0039d316-1c4b-4281-b951-d872f2087c98
* RefCounted types should not have public destructors, ipc/ editionrsleevi@chromium.org2012-04-285-59/+49
| | | | | | | | | | BUG=123295 TEST=none Review URL: http://codereview.chromium.org/10008108 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@134421 0039d316-1c4b-4281-b951-d872f2087c98
* NaCl: Pass the process handle to the broker rather than reopening itmseaborn@chromium.org2012-04-271-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, we would open the NaCl loader's Windows process handle by its PID in the NaCl broker (when attaching a Windows debug exception handler). But there is a potential race condition here: if the NaCl loader dies, and its PID is reused, we could be opening the wrong process. Fix this by opening the process handle in the browser process and passing it to the 64-bit NaCl broker. This requires fixing a bug in ipc_message_utils.h. This code could cope with sending a handle from a 64-bit process to a 32-bit process (NaCl broker to browser), but the DCHECK would fail when sending a handle from a 32-bit process to a 64-bit process (browser to NaCl broker). This change is in preparation for changing NaCl's Windows debug exception handler to attach on demand, which would allow untrusted NaCl code to cause the NaCl process to exit before OnDebugExceptionHandlerLaunched() runs. BUG=http://code.google.com/p/nativeclient/issues/detail?id=2618 TEST=run_inbrowser_exception_test in nacl_integration Review URL: https://chromiumcodereview.appspot.com/10174031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@134189 0039d316-1c4b-4281-b951-d872f2087c98
* Add ipc_channel_nacl to the untrusted build and fix all compile/link errors.bbudge@chromium.org2012-04-235-15/+49
| | | | | | | | | ppapi_proxy_untrusted.gyp should now build with a single link error for main. BUG=116317 TEST=builds with a single link error for main(). Review URL: https://chromiumcodereview.appspot.com/10167024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133519 0039d316-1c4b-4281-b951-d872f2087c98
* apk-based test runner work for android. 2 unit test bundles converted over ↵jrg@chromium.org2012-04-191-2/+51
| | | | | | | | | | | | | | | | | | | | | | | | (ipc, base). OFF by default; enable with a gyp var. E.g. GYP_DEFINES="$GYP_DEFINES gtest_target_type=shared_library" android_gyp Some useful commands: adb uninstall org.chromium.native_test adb install -r out/Release/base_unittests_apk/ChromeNativeTests-debug.apk adb shell am start -n org.chromium.native_test/org.chromium.native_test.ChromeNativeTestActivity For the moment, all apks can be built simultaneously but use the same activity name. Thus you cannot have more than one installed at the same time. BUG=None TEST= Review URL: http://codereview.chromium.org/10051021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133053 0039d316-1c4b-4281-b951-d872f2087c98
* Revert revert 132842xians@chromium.org2012-04-191-7/+71
| | | | | | | | | | | | | | | | If we are using blocking write, when the renderer stop getting the data without notifying the browser, it will hang the browser. This happens with some plugins which use the sync sockets provided by the Pepper. This patch change CancellableSyncSocket to be non-blocking on sending, so that we don't need to worry the whole browser hangs by one plugin application. Also, we remove the lock in audio_sync_reader.cc since it is not really needed if we don't set the socket_ to NULL when calling Close(). By doing this we allow the user to close the socket while another thread is writing to the socket. BUG=121152 TEST=ipc_tests TBR=tommi@chromium.org Review URL: https://chromiumcodereview.appspot.com/10124004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132975 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 132842 - If we are using blocking write, when the renderer stop ↵thestig@chromium.org2012-04-181-72/+7
| | | | | | | | | | | | | | | | | | | getting the data without notifying the browser, it will hang the browser. This happens with some plugins which use the sync sockets provided by the Pepper. This patch change CancellableSyncSocket to be non-blocking on sending, so that we don't need to worry the whole browser hangs by one plugin application. Also, we remove the lock in audio_sync_reader.cc since it is not really needed if we don't set the socket_ to NULL when calling Close(). By doing this we allow the user to close the socket while another thread is writing to the socket. BUG=121152 TEST=ipc_tests Review URL: http://codereview.chromium.org/10000004 TBR=xians@chromium.org Review URL: https://chromiumcodereview.appspot.com/10083064 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132888 0039d316-1c4b-4281-b951-d872f2087c98
* If we are using blocking write, when the renderer stop getting the data ↵xians@chromium.org2012-04-181-7/+72
| | | | | | | | | | | | | | | | without notifying the browser, it will hang the browser. This happens with some plugins which use the sync sockets provided by the Pepper. This patch change CancellableSyncSocket to be non-blocking on sending, so that we don't need to worry the whole browser hangs by one plugin application. Also, we remove the lock in audio_sync_reader.cc since it is not really needed if we don't set the socket_ to NULL when calling Close(). By doing this we allow the user to close the socket while another thread is writing to the socket. BUG=121152 TEST=ipc_tests Review URL: http://codereview.chromium.org/10000004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132842 0039d316-1c4b-4281-b951-d872f2087c98
* Add support for default values of IPC_STRUCT_MEMBER.jbates@chromium.org2012-04-166-10/+12
| | | | | | Review URL: http://codereview.chromium.org/10067023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132435 0039d316-1c4b-4281-b951-d872f2087c98
* ipc: don't treat replies with the unblock flag set as regular messagespiman@chromium.org2012-04-103-4/+123
| | | | | | | | | | | | | | | Old behavior would test should_unblock() before is_reply() so if both were set but TryToUnblockListener wouldn't return true (the corresponding Send isn't on top of the stack), it would queue the message as to be dispatched. This restores the correct order. BUG=122443 TEST=ipc_tests, in particular ReentrantReply Review URL: http://codereview.chromium.org/9960058 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131617 0039d316-1c4b-4281-b951-d872f2087c98
* Prevent reading invalid memory in IPC code caused by assumption of ↵fischman@chromium.org2012-04-092-4/+10
| | | | | | | | | | | | | | | | | | contiguity in std::deque<>. std::vector<int> guarantees contiguous storage (as of C++2003, 23.2.4p1, although in practice this is true with all known STL implementations), but std::deque<> typically uses linked chains of array blocks, so specifically *doesn't* provide contiguity once its size grows above its basic block size (usually 512bytes on our linux systems). BUG=117341 TEST=test in bug stops reproducing with this. Review URL: http://codereview.chromium.org/10019018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131443 0039d316-1c4b-4281-b951-d872f2087c98
* Browser side implementation of browser pluginfsamuel@chromium.org2012-04-061-0/+1
| | | | | | | | | | BUG=117897 TEST=manually Review URL: http://codereview.chromium.org/9924026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131054 0039d316-1c4b-4281-b951-d872f2087c98
* Make IPC channels track their peer process IDjschuh@chromium.org2012-04-058-6/+41
| | | | | | | | | | BrokerDuplicateHandle() requires the target process ID on Windows. Rather than plumb this into every channel class independently, I'm adding it at the top. TEST=IPCSyncChannelTest.Verified Review URL: http://codereview.chromium.org/9968111 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130817 0039d316-1c4b-4281-b951-d872f2087c98
* Require IPC hello for a verified channeljschuh@chromium.org2012-04-031-1/+5
| | | | | | | | | BUG=117627 TEST=IPCSyncChannelTest.Verified Review URL: http://codereview.chromium.org/9956085 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130346 0039d316-1c4b-4281-b951-d872f2087c98
* Initial implementation of an IPC adapter to expose Chrome IPC to Native Client.brettw@chromium.org2012-03-301-15/+18
| | | | | | | | | | | This provides an implementation of sendmsg and recvmsg approxinately to what we think NaCl will expose to Chrome. Since NaCl isn't ready yet in this regard, it's still a bit speculative. And there is no support for sending handles across which will be the tricky part. TEST=included unit test BUG=none Review URL: https://chromiumcodereview.appspot.com/9863005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129981 0039d316-1c4b-4281-b951-d872f2087c98
* IPC: change sync channel dispatch restriction to allow dispatch to other ↵piman@chromium.org2012-03-304-30/+202
| | | | | | | | | | | | | channels within the same "group" This prevents 4-way deadlocks with 2 renderers talking to 2 different pepper plugins. BUG=120530 TEST=RestrictedDispatch4WayDeadlock, load chromeos chrome with 2 gmail tabs (on 2 domains), quit and restore session multiple times. Review URL: https://chromiumcodereview.appspot.com/9917002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129944 0039d316-1c4b-4281-b951-d872f2087c98
* Add a stub version of IPC::Channel for Native Client code.brettw@chromium.org2012-03-302-0/+184
| | | | | | | | | | This isn't used yet, but will be necessary to get us linking when the build system is in better shape. Once that works we can start implementing this for real. Review URL: https://chromiumcodereview.appspot.com/9876003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129909 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 128679 - Speculative revert. xcodebuilders hosed between r128678 - ↵rsleevi@chromium.org2012-03-241-2/+2
| | | | | | | | | | | | | | | | | | 128680 in GYP phse, this is the only change that touched GYP files. apk-based test runner work. Not enabled yet. This CL is a combination of upstreaming, ndk/ant-ification, and other tweaks. BUG=None TEST= Review URL: http://codereview.chromium.org/9834037 TBR=jrg@chromium.org Review URL: https://chromiumcodereview.appspot.com/9852004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128685 0039d316-1c4b-4281-b951-d872f2087c98
* apk-based test runner work. Not enabled yet. This CL is a combination of ↵jrg@chromium.org2012-03-241-2/+2
| | | | | | | | | | | | upstreaming, ndk/ant-ification, and other tweaks. BUG=None TEST= Review URL: http://codereview.chromium.org/9834037 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128679 0039d316-1c4b-4281-b951-d872f2087c98
* Remove Pickle::WriteSize() now that it has no remaining callers. Also renamemdm@chromium.org2012-03-231-2/+2
| | | | | | | | | | | Pickle::WriteLong() to WriteLongUsingDangerousNonPortableLessPersistableForm() and add a strongly-worded comment against its use; it is used only for IPC which is safe. (These methods write variable amounts of data to pickles, depending on architecture, and aren't safe if pickles are persisted.) Review URL: http://codereview.chromium.org/9641005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128347 0039d316-1c4b-4281-b951-d872f2087c98
* Delete chrome_plugin_messages.h which is no longer usedjam@chromium.org2012-03-191-1/+0
| | | | | | Review URL: https://chromiumcodereview.appspot.com/9718019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127420 0039d316-1c4b-4281-b951-d872f2087c98
* Verify the child process with a secret hellojschuh@chromium.org2012-03-177-10/+227
| | | | | | | | | BUG=117627 TEST=IPCSyncChannelTest.Verified Review URL: http://codereview.chromium.org/9692035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127327 0039d316-1c4b-4281-b951-d872f2087c98
* JSONWriter cleanup: integrate pretty print into write options.ericdingle@chromium.org2012-03-161-2/+2
| | | | | | | | | | | BUG= TEST=base_unittests TBR=abodenha@chromium.org,ajwong@chromium.org,chocobo@chromium.org,mnissler@chromium.org,akalin@chromium.org,brettw@chromium.org,arv@chromium.org Review URL: http://codereview.chromium.org/9590002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127080 0039d316-1c4b-4281-b951-d872f2087c98
* Add base::StaticAtomicSequenceNumber.pliard@chromium.org2012-03-131-4/+4
| | | | | | | | | | | | This patch also replaces the global AtomicSequenceNumber variables with StaticAtomicSequenceNumber in order to remove static initializers. BUG=94925 Review URL: http://codereview.chromium.org/9415039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126376 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-12 04:33:59 +0000