[fidl][crash] fx format-code crash.fidl
* this removed the ordinals
* this indents correctly the enum and the return values
TESTED=`crasher` on vim2 and NUC
Change-Id: Ia343fdaf49e3dd3c24a2cae27f4a8073dc5c7018
diff --git a/system/fidl/fuchsia-crash/crash.fidl b/system/fidl/fuchsia-crash/crash.fidl
index 65777b1..997c7f9 100644
--- a/system/fidl/fuchsia-crash/crash.fidl
+++ b/system/fidl/fuchsia-crash/crash.fidl
@@ -13,9 +13,9 @@
// Enumerates the languages with managed runtimes for which we might want a
// specific handling of the thrown exceptions.
enum ManagedRuntimeLanguage {
- UNKNOWN_LANGUAGE = 0;
- OTHER_LANGUAGE = 1;
- DART = 2;
+ UNKNOWN_LANGUAGE = 0;
+ OTHER_LANGUAGE = 1;
+ DART = 2;
};
// Analyzes crashed processes, string exceptions from managed runtimes or
@@ -33,10 +33,10 @@
//
// |exception_port| is the port on which the exception was delivered and
// can be passed to zx_task_resume_from_exception().
- 1: HandleNativeException(handle<process> process,
- handle<thread> thread,
- handle<port> exception_port)
- -> (zx.status status);
+ HandleNativeException(handle<process> process,
+ handle<thread> thread,
+ handle<port> exception_port)
+ -> (zx.status status);
// Requests that the crash analyzer handles the exception thrown in the
// managed runtime for the given |language|.
@@ -47,16 +47,16 @@
// The behavior of this method varies depending on the implementation, but
// a typical implementation might print the exception message and stack
// trace to the system log or upload a crash report to a server.
- 2: HandleManagedRuntimeException(ManagedRuntimeLanguage language,
- string:MAX_COMPONENT_URL_LENGTH componentUrl,
- string:MAX_EXCEPTION_MSG_LENGTH exception,
- fuchsia.mem.Buffer stackTrace)
- -> (zx.status status);
+ HandleManagedRuntimeException(ManagedRuntimeLanguage language,
+ string:MAX_COMPONENT_URL_LENGTH componentUrl,
+ string:MAX_EXCEPTION_MSG_LENGTH exception,
+ fuchsia.mem.Buffer stackTrace)
+ -> (zx.status status);
// Requests that the crash analyzer processes the kernel panic crash log.
//
// The behavior of this method varies depending on the implementation, but
// a typical implementation might print the crash log to the system log or
// upload a crash report to a server with the log as attachment.
- 3: ProcessKernelPanicCrashlog(fuchsia.mem.Buffer crashlog) -> (zx.status status);
+ ProcessKernelPanicCrashlog(fuchsia.mem.Buffer crashlog) -> (zx.status status);
};