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

REPL cannot display arrays #5701

Closed
mkriele opened this issue Feb 6, 2014 · 6 comments
Closed

REPL cannot display arrays #5701

mkriele opened this issue Feb 6, 2014 · 6 comments

Comments

@mkriele
Copy link
Contributor

mkriele commented Feb 6, 2014

I get the following error

julia> x=[1,2]
2-element Array{Int64,1}:
Evaluation succeeded, but an error occurred while showing value of type Array{Int64,1}:
ERROR: premature end of integer: "24"
 in error at error.jl:21
 in parseint_nocheck at string.jl:1486
 in parseint_nocheck at string.jl:1523
 in parseint at string.jl:1526
 in writemime at repl.jl:21
 in display at multimedia.jl:117
 in display at multimedia.jl:119
 in display at multimedia.jl:151

The premature end of integer: "24" appears to be somewhat arbitrary. The error message above was obtained in the shell that opens upon double-clicking the julia application. However, when I call julia from emacs (using ESS) the ERROR-line reads

ERROR: premature end of integer: "25"

Otherwise the error message is the same.

@mkriele
Copy link
Contributor Author

mkriele commented Feb 7, 2014

I changed the title to a more accurate one. The methods show, showall, showcompact, print, println all work fine. But if I simply type an Array into the REPL, the REPL does not echo it but gives the above error message.
In the meanwhile, the mac binary referenced in my original title has been replaced to fix an unrelated issue. The issue reported here still persists with the new binary, and I do not know whether it is mac specific or not. For me this issue appeared when I upgraded vorm Julia 0.2 to 0.3 prerelease.

@vtjnash
Copy link
Member

vtjnash commented Feb 8, 2014

duplicate of #5647

@vtjnash vtjnash closed this as completed Feb 8, 2014
@mkriele
Copy link
Contributor Author

mkriele commented Feb 8, 2014

It may be entirely my lack of understanding, but I do not see why this is a duplicate of #5647. As far as I understand, sys.dll is windows-specific, while I have been using a Mac (10.9). I understand from the the first post of #5647 that the REPL used by GaborOslany can display arrays and crashes upon a further command. Gabor also reported that his problem only appears on a 32 bit Vista but not on 64 bit Vista. The OS used by me is 64 bit.

Sent from my iPad

On Feb 7, 2014, at 22:39, Jameson Nash notifications@github.com wrote:

duplicate of #5647


Reply to this email directly or view it on GitHub.

@vtjnash
Copy link
Member

vtjnash commented Feb 8, 2014

On Mac, the file is called sys.dylib, but it almost certainly the same issue. It's actually a exact duplicate of an older issue (which was fixed at the time), but I couldn't find the number.

@staticfloat
Copy link
Member

@mkriele The easy way to tell is to search for sys.dylib inside of the lib/julia folder in your Julia installation. Since you're on a mac, that would be in: Julia-0.3.0-prerelease-<githash>.app/Contents/Resources/julia/lib/julia/, where githash is a long alphanumeric identifier for the version of Julia that was built. If sys.dylib exists there, please remove it and see if the issue persists.

@mkriele
Copy link
Contributor Author

mkriele commented Feb 8, 2014

Thanks Jameson and Elliot, you are right. I had the file sys.dylib in the app package and once I trashed it my issue was gone.

On 2014-02-07 , at 23:20, Elliot Saba notifications@github.com wrote:

@mkriele The easy way to tell is to search for sys.dylib inside of the lib/julia folder in your Julia installation. Since you're on a mac, that would be in: Julia-0.3.0-prerelease-.app/Contents/Resources/julia/lib/julia/, where githash is a long alphanumeric identifier for the version of Julia that was built. If sys.dylib exists there, please remove it and see if the issue persists.


Reply to this email directly or view it on GitHub.

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

3 participants