crash with input longer than line width
See original GitHub issueI’m using iPython 5.1.0 with the latest prompt_toolkit package (1.0.7). iPython crashes every time I input a line with more characters than my terminal’s current line width. The crash report generated with verbose_crash=True
is attached.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
scanf() without field width limits can crash with huge input data
Add a field width specifier to fix this problem. Sample program that can crash: #include <stdio. h> int main() { char c[5]; scanf("%s",...
Read more >Application crashes when you input text at the beginning of ...
You move the cursor to the beginning of the first line, and then you type a character. In this scenario, the application crashes....
Read more >gpt2 generation crashes when using `past` for some output ...
I am using run_generation.py to generate text from gpt2, but with the code slightly changed to make use of past to cache hidden...
Read more >crash(8) - Linux manual page - man7.org
The crash utility is designed to be independent of Linux version ... If it is the string "input", a page describing the various...
Read more >Fuzzing with afl-fuzz — AFL 2.53b documentation
In this mode, the fuzzer takes one or more crashing test cases as the input, and uses its feedback-driven fuzzing strategies to very...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Pinging @jonathanslenders . Here’s the last couple of frames from the traceback, for convenience:
IPython in general should try to be resilient against anything user-configurable. One simple option is we could run the prompt once ourselves at startup to validate it.