Github messages for voidlinux
 help / color / mirror / Atom feed
From: howtologinquickwiththirtyninecharacters <howtologinquickwiththirtyninecharacters@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] cutter: it's not built with any decompiler unlike the official AppImage package
Date: Sun, 19 Apr 2020 21:49:30 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21159@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]

New issue by howtologinquickwiththirtyninecharacters on void-packages repository

https://github.com/void-linux/void-packages/issues/21159

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *Void 5.4.33_2 x86_64 GenuineIntel uptodate rrFFFFFF*
* package:  
  *cutter-1.10.2_2*

### Expected behavior

Cutter has at least one decompiler in the dropdown menu (this is the default behavior of the official releases, you can get the AppImage to test that from [here](https://github.com/radareorg/cutter/releases))

### Actual behavior

The decompiler dropdown is disabled and displays no options.

### Steps to reproduce the behavior

1. Install `cutter`
2. Run it (the executable is called `Cutter` with an uppercase C)
3. Select any file (let's use `/bin/cat` as an example)
4. Click Open
5. Click Ok on the analysis screen
6. Select the Decompiler tab on the bottom (if it is not visible click on the Windows menu and enable it)
7. Confirm that the Decompiler dropdown menu on the bottom right is empty (the official AppImage display Ghidra as the default decompiler)

             reply	other threads:[~2020-04-19 19:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19 19:49 howtologinquickwiththirtyninecharacters [this message]
2020-04-21 20:46 ` ericonr
2020-04-21 20:49 ` jnbr
2020-05-06  5:41 ` ericonr
2020-05-08  0:27 ` jnbr
2020-05-12 12:46 ` howtologinquickwiththirtyninecharacters
2020-05-12 12:49 ` howtologinquickwiththirtyninecharacters
2022-04-16  2:02 ` github-actions
2022-04-30  2:13 ` [ISSUE] [CLOSED] " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21159@inbox.vuxu.org \
    --to=howtologinquickwiththirtyninecharacters@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).