Adding untrusted crash dump / stack trace tests.

src/trusted/service_runtime/build.scons

Index: src/trusted/service_runtime/build.scons
diff --git a/src/trusted/service_runtime/build.scons b/src/trusted/service_runtime/build.scons
index 503ba1e993b0c7948ab87c43b176145d191a56dc..45129f9938866da69e2b1fb7e02f962972ef9751 100644
--- a/src/trusted/service_runtime/build.scons
+++ b/src/trusted/service_runtime/build.scons
@@ -319,6 +319,13 @@ if ((not env.Bit('coverage_enabled') or not env.Bit('windows')) and
   sel_main_objs = [env.ComponentObject('sel_main.c')] + r_debug_objs
   SEL_LDR_NODE = env.ComponentProgram('sel_ldr', sel_main_objs,
                                       EXTRA_LIBS=sel_ldr_libs)
+  # TODO(bradnelson): drop once exceptions are available by default.
+  env_exc = env.Clone()
+  env_exc.Append(CPPDEFINES=['NACL_EXCEPTION_HANDLING_REQUESTED'])
+  exc_sel_main_objs = [
+      env_exc.ComponentObject('sel_main_exc', 'sel_main.c')] + r_debug_objs

[Mark Seaborn, 2012/02/06 17:35:04]

This sets a bad precedent.  I don't want to start building different variants of
sel_ldr that differ only in whether an option is enabled or disabled.  If we did
this for more options there would be an exponential explosion.  Can you use an
environment variable for enabling exception handling instead?

[bradn, 2012/02/06 19:26:59]

Done.
Odd, I didn't know the environment get propagated thru like that.
Is that wise?
I had the impression is was scrubbed.

+  exc_SEL_LDR_NODE = env_exc.ComponentProgram('sel_ldr_exc', exc_sel_main_objs,
+                                              EXTRA_LIBS=sel_ldr_libs)
   if env.Bit('mac'):
     # This target exists only to check that the service_runtime code
     # can successfully be linked into a Mac OS X dynamic library.  Our