Closed staticfloat closed 11 years ago
Interestingly, building a Debug version and running that inside of gdb
doesn't crash, although the text layout does still go crazy.
I don't get a crash, but it definitely behaves oddly. The Display all 1860 possibilities?
message appears, but before I can answer it starts printing all the completions, leaving the terminal in a strange state. This only seems to happen in cases with enough completions to print that message. Surely there is something unhealthy about telling readline to read from /dev/null.
@vtjnash
Thanks for looking into this.
It appears that the segfault only happens when running Julia inside of tmux
. Running julia inside tmux
results in output that looks like this: http://i.imgur.com/t58hFus.png
This is after typing "Base.
@vtjnash Unfortunately I don't see a simple way to fix this within the current framework. We have readline'd ourselves into a corner.
it certainly seems that way. i'm seeing if we can feed readline with a pipe (created by libuv) instead of rl_stuff_char.
seems like the best thing to do is comment out the /dev/null stdin redirection for the v0.1 release, until we can replace readline
This has been fixed for me. Can anyone else reproduce this error? Otherwise I will close.
This i what i am getting,,
Program received signal SIGABRT, Aborted.
0x96a63a6a in __pthread_kill ()
(gdb) bt
#0 0x96a63a6a in __pthread_kill ()
#1 0x9590bacf in pthread_kill ()
#2 0x0391357b in abort ()
#3 0x03825f7b in abort_message ()
#4 0x03823a25 in default_terminate ()
#5 0x006170c1 in _objc_terminate ()
#6 0x03775652 in std::terminate ()
#7 0x00617039 in objc_terminate ()
#8 0x038a4027 in _dispatch_client_callout ()
#9 0x038947d5 in _dispatch_main_queue_callback_4CF ()
#10 0x02448af5 in __CFRunLoopRun ()
#11 0x02447f44 in CFRunLoopRunSpecific ()
#12 0x02447e1b in CFRunLoopRunInMode ()
#13 0x0403c7e3 in GSEventRunModal ()
#14 0x0403c668 in GSEventRun ()
#15 0x0098465c in UIApplicationMain ()
#16 0x000a5187 in main ()
[pao: formatting]
Our poor early issues. @railskipl, just a heads up, be sure you code-quote (single backtick inline, triple backtick for block) console output and Julia code, since the GitHub autolinker may otherwise drop cross-references in unrelated issues (as it did here with the #nn
from the backtrace) or ping random people whose usernames happen to match the names of Julia macros (due to Julia's @macro
syntax). Thanks!
+1 to close. Can't replicate either.
Going to go ahead and close this. @railskipl, if you can reproduce on an up-to-date build of Julia, please open a new issue for it.