Fix AmIBundled for command-line executions.

base/mac/foundation_util.mm

Index: base/mac/foundation_util.mm
diff --git a/base/mac/foundation_util.mm b/base/mac/foundation_util.mm
index 1d33391f1e2341da72732c14b2a20e99520fb9d9..40bcb4db579622616eb556a5f629a2990e6f6af9 100644
--- a/base/mac/foundation_util.mm
+++ b/base/mac/foundation_util.mm
@@ -36,8 +36,10 @@ static bool UncachedAmIBundled() {
     return g_override_am_i_bundled_value;
 
   NSBundle* bundle = base::mac::OuterBundle();
-  NSArray* bundle_parts = [[bundle bundlePath] pathComponents];
-  NSArray* executable_parts = [[bundle executablePath] pathComponents];
+  NSArray* bundle_parts =
+      [[[bundle bundlePath] stringByStandardizingPath] pathComponents];

[Mark Mentovai, 2013/10/25 22:54:56]

This isn’t really correct. The tilde expansion it might do is wrong (in case a
directory begins with a ~ and you launch it as \~whatever/Google\ Chrome.app/… .

Which relative path invocations are you concerned about here?

https://developer.apple.com/library/mac/documentation/cocoa/Reference/Foundat...

says that this only resolves .. in absolute paths. And it says that in that
case, it uses stringByResolvingSymlinksInPath, which we don’t want to use here
because it does disk I/O.

+  NSArray* executable_parts =
+      [[[bundle executablePath] stringByStandardizingPath] pathComponents];
 
   // Bundled executables are exactly three levels deeper than their bundle.
   // Non-bundled executables have a fake bundle with a bundle path of their