Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segfault #8

Open
brainard52 opened this issue May 14, 2021 · 2 comments
Open

Segfault #8

brainard52 opened this issue May 14, 2021 · 2 comments

Comments

@brainard52
Copy link

I built with gcc included in macOS developer tools on an M1 MacBook Pro running macOS 11.3 (20E232).

MacBook-Pro vtGBte % gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
Apple clang version 12.0.5 (clang-1205.0.22.9)
Target: arm64-apple-darwin20.4.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

When I ran gbt --help, it tried to prompt to create a file called "help". When I pressed q at that prompt, it segfaulted.

@paul-arutyunov
Copy link
Owner

It actually doesn’t have that feature. Built-in help card can be invoked by h. As for the segfault, it didn’t occur for me.

Looks like this tool needs a bit of a resurrection.

@brainard52
Copy link
Author

brainard52 commented May 14, 2021

It actually doesn’t have that feature. Built-in help card can be invoked by h.

--help is somewhat standard, and I didn’t read the documentation prior to trying it.

As for the segfault, it didn’t occur for me.

This is likely due to the change in architecture. M1 is a custom ARM architecture, so tolerances will probably be different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants