Remove old flags from about:flags and add new ones instead.

chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
===================================================================
--- chrome/app/generated_resources.grd	(revision 154320)
+++ chrome/app/generated_resources.grd	(working copy)
@@ -5306,18 +5306,12 @@
       <message name="IDS_FLAGS_ENABLE_NACL_EXCEPTION_HANDLING_DESCRIPTION" desc="Description of the 'Enable Native Client hardware exception handling' lab.">
         Enable support for Native Client hardware exception handling.
       </message>
-      <message name="IDS_FLAGS_NACL_GDB_NAME" desc="Name of the 'Debug Native Client applications at startup' lab">
-        Debug Native Client applications at startup.
+      <message name="IDS_FLAGS_ENABLE_NACL_DEBUG_NAME" desc="Name of the 'NaCl debug stub' lab.">

[Mark Seaborn, 2012/08/31 20:10:18]

Maybe write 'NaCl GDB debug stub' to make things clearer.

[halyavin, 2012/09/03 12:04:39]

Done.

+        Native Client debugging

[Mark Seaborn, 2012/08/31 20:10:18]

Maybe 'Native Client GDB-based debugging'?

[halyavin, 2012/09/03 12:04:39]

Done.

       </message>
-      <message name="IDS_FLAGS_NACL_GDB_DESCRIPTION" desc="Description of the 'Debug Native Client applications at startup' lab.">
-        Set path to nacl-gdb debugger. It will be attached to NaCl applications at startup.
+      <message name="IDS_FLAGS_ENABLE_NACL_DEBUG_DESCRIPTION desc="Description of the 'NaCl debug stub' lab.">
+        Enable debug stub that stops Native Client applications at startup and waits for nacl-gdb debugger from NaCl SDK.

[Mark Seaborn, 2012/08/31 20:10:18]

Maybe: "Enable GDB debug stub.  This will stop a Native Client application on
startup and wait for nacl-gdb (from the NaCl SDK) to attach to it."

Do you think this is useful to enable via about:flags?  If someone enables it
and forgets about it, they will find that NaCl apps mysteriously fail to start,
without any indication of why.

It might avoid potential confusion if we only support this via the command line.

Also, currently '--enable-nacl-debug' also requires '--no-sandbox', so enabling 
it via about:flags alone is not very useful.  While we could make
nacl_process_host.cc add kNoSandbox automatically, that is a little scary. 
Maybe we can put effort into making the debug stub work without --no-sandbox
rather than adding --no-sandbox implicitly?

[halyavin, 2012/09/03 12:04:39]

Done. I think we should address no-sandbox issue in a separate CL(s).

[halyavin, 2012/09/04 12:10:30]

I investigated the issue and talked with people from ChromeOS team. They
explained that adding --no-sandbox is not possible without switching to dev mode
and changing OS image (and sandbox can't be disabled for NaCl without disabling
it for all processes). If, on the other hand, we could make debug stub work
without --no-sandbox, one can debug NaCl applications in ChromeOS even without
switching to dev mode.

       </message>
-      <message name="IDS_FLAGS_NACL_GDB_SCRIPT_NAME" desc="Name of the 'Script executed by Native Client application debugger at startup' lab.">
-        Script to be executed by nacl-gdb at startup.
-      </message>
-      <message name="IDS_FLAGS_NACL_GDB_SCRIPT_DESCRIPTION" desc="Description of the 'Script executed by Native Client application debugger at startup' lab.">
-        Set path to script with gdb commands which will be executed by nacl-gdb at startup.
-      </message>
       <message name="IDS_FLAGS_ENABLE_PNACL_NAME" desc="Name of the 'Enable Portable Native Client' lab.">
         Portable Native Client.
       </message>