fuchsia_dash

Namespaces

enum class LauncherError : uint32_t

Name	Value	Comments
kInternal	1u	Launcher encountered an unspecified error
kBadMoniker	2u	Moniker could not be parsed by launcher
kInstanceNotFound	3u	No instance was found matching the moniker
kRealmQuery	4u	Error occurred using fuchsia.sys2.RealmQuery
kProcessLauncher	5u	Error occurred using fuchsia.process.Launcher
kDashBinary	6u	Error loading dash binary
kPty	7u	Error occurred involving the PTY
kInstanceNotResolved	8u	Instance is not in a resolved state, so there is nothing to explore
kPackageResolver	9u	Error occurred using fuchsia.pkg.PackageResolver
kToolsCannotResolve	10u	Error resolving tools package
kBadUrl	11u	URL could not be parsed by launcher
kToolsBinaryRead	12u	Error reading a binary from a tools package
kNonUniqueBinaryName	13u	A binary name was repeated
kProcessResolver	14u	Error occurred using fuchsia.process.Resolver
kVmexResource	15u	Error occurred using fuchsia.kernel.VmexResource
kResolveTargetPackage	16u	Error resolving the package that is to be explored.

Standard errors for the Launcher protocol

Defined at line 19 of file fidling/gen/sdk/fidl/fuchsia.dash/fuchsia.dash/cpp/fidl/fuchsia.dash/cpp/common_types.h

enum class DashNamespaceLayout : uint32_t

Name	Value	Comments
kNestAllInstanceDirs	1u	All instance directories are nested under subdirectories. e.g - namespace is under /ns, outgoing dir is under /out, etc.
kInstanceNamespaceIsRoot	2u	The instance namespace is the root of the dash shell. Several ELF binaries and libraries in Fuchsia assume that directories like `svc` and `dev` will be at the root. As a result, this layout should be more compatible than nesting for running Fuchsia ELF binaries in the shell.

The namespace layout to create for the dash process.

Defined at line 87 of file fidling/gen/sdk/fidl/fuchsia.dash/fuchsia.dash/cpp/fidl/fuchsia.dash/cpp/common_types.h