crownedgrouse/geas

Guess Erlang Application Scattering

geas's Issues

Detect use of undocumented OTP functions

Hi! Can GEAS detect use of undocumented OTP modules, functions and types?

If not, would you be willing to add such feature?

AFAIK, there is no list of documented functions in OTP but it should be possible to extract it from the documentation xml files.

Complete support of source files

If we don't know which OTP release a project will compile with, how will we be able to run Geas? As of now it only runs on compiled projects!

Please add support for source files (erlang at least).
Once support is ready, we can add Geas output to other.erldocs.com. There's an issue there already erldocs/other.erldocs.com#88

rebar3 geas is hanging

The following project https://github.com/walter-weinmann/ocparse has problems with rebar3 geas.

trim_all option is not available in 17.5 for binary:split

See crownedgrouse/geas_rebar3#7

Uncaught error: badmatch

I get the following error when i run rebar3 geas

===> Uncaught error in rebar_core. Run with DEBUG=1 to see stacktrace
===> Uncaught error: {badmatch,
                                {error,
                                    "Application Resource File (.app.src) not found, neither .erl files. Aborting."}}
===> Stack trace to the error location: [{geas,'-compat/2-fun-1-',1,
                                                 [{file,
                                                   "/home/byaruhaf/projects/Erlang_Project/otto/_build/default/plugins/geas/src/geas.erl"},
                                                  {line,1118}]},
                                                {lists,flatmap,2,
                                                 [{file,"lists.erl"},
                                                  {line,1249}]},
                                                {lists,flatmap,2,
                                                 [{file,"lists.erl"},
                                                  {line,1249}]},
                                                {geas,compat,2,
                                                 [{file,
                                                   "/home/byaruhaf/projects/Erlang_Project/otto/_build/default/plugins/geas/src/geas.erl"},
                                                  {line,1117}]},
                                                {geas,compat,2,
                                                 [{file,
                                                   "/home/byaruhaf/projects/Erlang_Project/otto/_build/default/plugins/geas/src/geas.erl"},
                                                  {line,1153}]},
                                                {geas_rebar3,do,1,
                                                 [{file,
                                                   "/home/byaruhaf/projects/Erlang_Project/otto/_build/default/plugins/geas_rebar3/src/geas_rebar3.erl"},
                                                  {line,34}]},
                                                {rebar_core,do,2,
                                                 [{file,
                                                   "/home/travis/build/rebar/rebar3/_build/default/lib/rebar/src/rebar_core.erl"},
                                                  {line,125}]},
                                                {rebar3,main,1,
                                                 [{file,
                                                   "/home/travis/build/rebar/rebar3/_build/default/lib/rebar/src/rebar3.erl"},
                                                  {line,56}]}]

Auto imported functions from the erlang module not detected

I'm using the master version of the Rebar 3 plugin, and Geas does not detect the usage of auto imported functions from the erlang module, e.g. binary_to_integer/2 or integer_to_binary/2.

If I add the erlang:... prefix it works.

Let me know if you need any more info.

Do plugin for rebar 3

`geas_beam.hrl`'s `is_native_from_file/1` crashes for missing `compile_info` "key"

👋, I'm using geas in a project that contains a BEAM file called certifi.beam.

For that file (as described in geas_beam.hrl's is_native_from_file/1)

{ok,{_,[{compile_info, L}]}} = beam_lib:chunks(Bn, [compile_info]),
{options, O} = lists:keyfind(options, 1, L),  % lists:keyfind/3 returns false

is false (i.e. there's a badmatch), which means geas_api.hrl's info/1 goes to the catch which ends up in {error, Reason}.

certifi.beam has just (for that compile_info) [{version,"8.2.6.3"}].

For whatever reason (still didn't dig into that) this hides the initial "output" panel where GEAS shows e.g.

   R15                   26.1       Geas database                      2.7.14
---Min--------Arch-------Max----------------------------------------------------
   21.0                             api                                 0.1.0
   21.0                             boad                               3.16.8
                                    certifi                             2.6.1
...
--------------------------------------------------------------------------------
   25.0                  20.3       Global project                      local

which hinders usability.

I wonder if keyfind should be more relaxed, there, and actually not crash but allow returning false from is_native_from_file/1.

I'm Ok to pull request; but I'd prefer to understand the reason behind the specific pattern match before doing so... Thanks.

Remove reports of `Shell got {'EXIT',<pid>,normal}` in output

This is happening to me in Erlang/OTP 26.1.1, at least.

I'll try to find the culprit and pull request to get rid of these messages.

Compilation error in Erlang 27

maybe is a reserved word now, and should be escaped like 'maybe':

rel_info({tls_handshake_1_3,maybe,0}) -> {"24.0", "25.3", ">=24.0 <=25.3", true};