Skip to content

no indication when process exits with a signal #5960

@toffaletti

Description

@toffaletti

Describe the bug

I have a process that crashes with SIGTRAP on macOS. Running the executable under nushell gives no indication the process exited because of a fatal signal.

Other shells have more to say when this occurs.
fish: terminated by signal SIGTRAP (Trace or breakpoint trap)
bash: Trace/BPT trap: 5
zsh: zsh: trace trap

How to reproduce

  1. Run a command that exits with SIGTRAP (such as a binary that is not properly code signed on macOS)

Expected behavior

I expected nushell to give some indication the process exited with a signal.

Screenshots

No response

Configuration

key value
version 0.65.0
branch
commit_hash
build_os macos-x86_64
build_target x86_64-apple-darwin
rust_version rustc 1.61.0 (fe5b13d68 2022-05-18)
rust_channel stable-x86_64-apple-darwin
cargo_version cargo 1.61.0 (a028ae42f 2022-04-29)
pkg_version 0.65.0
build_time 2022-07-05 14:34:47 -07:00
build_rust_channel release
features database, dataframe, default, trash, which, zip
installed_plugins

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    A:external-commandsIssues related to external commandsA:signal-cancelProblems with how executions react to signals or attempts at cancellation (CTRL-C)category:enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions