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

No error message in Eclipse consloe/erang shell #128

Open
drapostolos opened this Issue Nov 6, 2013 · 3 comments

Comments

Projects
None yet
2 participants
@drapostolos

drapostolos commented Nov 6, 2013

when I execute the following command:
io:format("error ~p", []).
in the eclipse console (with a erlang shell running), it does not print out any error message, why?

If I execute the same line in a standalone erlang shell/window, it givers the following error:
** exception error: bad argument
in function io:format/3
called as io:format(<0.25.0>,"error ~p",[])

image

image

@vladdu

This comment has been minimized.

Show comment
Hide comment
@vladdu

vladdu Nov 6, 2013

Contributor

This is because we are not interacting with the shell directly, but send the call as a RPC. This makes the exception get "lost", which is not good. I will fix it.
Thanks for the report!

Contributor

vladdu commented Nov 6, 2013

This is because we are not interacting with the shell directly, but send the call as a RPC. This makes the exception get "lost", which is not good. I will fix it.
Thanks for the report!

@drapostolos

This comment has been minimized.

Show comment
Hide comment
@drapostolos

drapostolos Nov 6, 2013

Thanks :)
Will this fix apply to all calls to other processes? I'm an erlang newbee, and going through this tutorial (http://learnyousomeerlang.com/designing-a-concurrent-application). And when my module is spawning new processes, any errors in the new processes are lost. Which makes the erlang shEll look like it just freezes. Makes it very hard to debug...

drapostolos commented Nov 6, 2013

Thanks :)
Will this fix apply to all calls to other processes? I'm an erlang newbee, and going through this tutorial (http://learnyousomeerlang.com/designing-a-concurrent-application). And when my module is spawning new processes, any errors in the new processes are lost. Which makes the erlang shEll look like it just freezes. Makes it very hard to debug...

@vladdu

This comment has been minimized.

Show comment
Hide comment
@vladdu

vladdu Nov 6, 2013

Contributor

Well, there are many ways for exceptions and error messages to get lost. If the cause is the interaction with the erlide console, the my goal is to fix that.

The erlide console is a so-called remote shell and some output (most notably from error_logger and SASL) goes directly to stdout. Due to some quirks of Eclipse, it is not easy to get that output, but it's on the list of things to look at.

Contributor

vladdu commented Nov 6, 2013

Well, there are many ways for exceptions and error messages to get lost. If the cause is the interaction with the erlide console, the my goal is to fix that.

The erlide console is a so-called remote shell and some output (most notably from error_logger and SASL) goes directly to stdout. Due to some quirks of Eclipse, it is not easy to get that output, but it's on the list of things to look at.

@vladdu vladdu removed the assembla label Jul 5, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment