summaryrefslogtreecommitdiffstats
path: root/chrome_frame/utils.cc
diff options
context:
space:
mode:
authorcmasone@google.com <cmasone@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2010-01-22 17:59:18 +0000
committercmasone@google.com <cmasone@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2010-01-22 17:59:18 +0000
commit0aacf9c51ec5e715773f23bca7f9c7c75f34b5ea (patch)
tree2bf991aa0f029a8078ede5fac502b6bc8c7b5308 /chrome_frame/utils.cc
parent79276d8f304ed8e57fcc7d25b1e415ff347049ef (diff)
downloadchromium_src-0aacf9c51ec5e715773f23bca7f9c7c75f34b5ea.zip
chromium_src-0aacf9c51ec5e715773f23bca7f9c7c75f34b5ea.tar.gz
chromium_src-0aacf9c51ec5e715773f23bca7f9c7c75f34b5ea.tar.bz2
The login manager didn't gracefully degrade in the event that libcros.so couldn't be loaded. it segfaulted. This makes it not die, disable login, and tell the user. Not so much so that a user could do anything about it, but so that devs can run chromeos chrome on their linux machines and develop the login UI there.
BUG=NONE TEST=run chromium for chromium OS on your linux box with the --login-manager flag, and watch it not segfault :-) Review URL: http://codereview.chromium.org/555036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36870 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame/utils.cc')
0 files changed, 0 insertions, 0 deletions