Opened 9 months ago
Last modified 3 weeks ago
#69235 assigned defect
watchman: trace trap — at Version 1
Reported by: | phiz118 | Owned by: | danchr (Dan Villiom Podlaski Christiansen) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.9.0 |
Keywords: | Cc: | ||
Port: | watchman, libunwind |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
~ % sudo port install watchman ---> Computing dependencies for watchman ---> Fetching archive for watchman ---> Attempting to fetch watchman-2023.11.13.00_2.darwin_23.arm64.tbz2 from https://packages.macports.org/watchman ---> Attempting to fetch watchman-2023.11.13.00_2.darwin_23.arm64.tbz2.rmd160 from https://packages.macports.org/watchman ---> Installing watchman @2023.11.13.00_2 ---> Activating watchman @2023.11.13.00_2 ---> Cleaning watchman ---> Scanning binaries for linking errors ---> No broken files found. ---> No broken ports found. ~ % watchman zsh: trace trap watchman
Apple M1 Max
Sonoma 14.3
Change History (2)
comment:1 Changed 9 months ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Owner: | set to danchr |
Status: | new → assigned |
Summary: | This port doesn't seem to work after install → watchman: trace trap |
Changed 8 months ago by raxod502-plaid (Radon Rosborough)
Attachment: | watchman-2024-02-15-083312.ips added |
---|
crash log
Note: See
TracTickets for help on using
tickets.
A quick search of "trace trap" suggests it means the program received a
SIGTRAP
signal, and that this would occur if there were an unhandled exception.I'm not sure if this situation would generate a crash log in ~/Library/Logs/DiagnosticReports. If it does, please attach it.