Trace from cmdline?

[ruanpienaar]

Would it be useful if you were able to have erlyberly already start tracing after being connected?

Passing in command line arguments, like, java -jar erlyberly.jar -trace M F A ( something in that region)

[andytill]

Yes! This could help a lot.

I have been having a problem where I want to trace nodes that get started up and shut down quickly, for example, in common test runs. In this scenario it is not possible to use erlyberly and generally a bit difficult to apply traces:

• Have an option to keep attempting to connect when erlyberly first starts up.
• Allow specifying traces in a file containing one MFA per line in M:F/A format.

Modules might not be loaded somodule_info should be called on them to reload them. I'm not sure what the behaviour is for tracing modules that are not yet loaded.

This expands the scope quite a lot though, what do you think?

[ruanpienaar]

That sounds great! There could be a configuration/preferences scene/window, for "Auto-Connecting" and "Default Tracing". All of this sounds great, i can look into it.

[ruanpienaar]

Would Commons CLI be ok to use?

[andytill]

Most of this functionality is moved into the UI so could choosing a text file of MFAs also be on the connection window? The JavaFX file chooser can be used to select a file.

[ruanpienaar]

just as we create the .erlyberly, could we create something like .erlyberly_traces, or maybe even make a directory ?

I'm trying to extend the CMD line arguments, as i'd like to use that. I'm aiming for opening 4 EB's at the same time, with diff node names, etc.

[ruanpienaar]

Would a text box be good enough as the first attempt ? format: [ module:function/arity ], or 3 text boxes even [ module ] : [ function ] / [ arity ] ?

[andytill]

Hadn't thought of the case of starting multiple nodes from the command line. Feel free to add Commons CLI, used it before and it is decent and doesn't bloat the jar. Please add the flags to the README. Good luck!