DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
that is now much better. What I found is:
1. there is a SIGSEGV, which could have been used to go further, but unfortunately
2. the beginning of that strace log is missing (you only posted the last 9200 lines).
Please retry and try to post the complete file.
you can use wc -l /tmp/ilspy.strace to print the number of lines of that file.
But remember perhaps you need to generate it again, most probably it was/will automatically deleted when you reboot your host.
that is now much better. What I found is:
1. there is a SIGSEGV, which could have been used to go further, but unfortunately
2. the beginning of that strace log is missing (you only posted the last 9200 lines).
Please retry and try to post the complete file.
you can use wc -l /tmp/ilspy.strace to print the number of lines of that file.
But remember perhaps you need to generate it again, most probably it was/will automatically deleted when you reboot your host.
https://pastebin.com/JcxnurnL For some reason I cannot get the complete file. I used the first 2 lines only as reference. When I run
yes, because your terminal cannot handle it. I don't know what kind of terminal you have, but you need to set properties to be able to handle 10 thousand or even more lines.
Just to understand: we know (reading your last trace) the SIGSEGV occurred in process 8646, but we have no idea how it was started (what is it), because that part is missing.
yes, because your terminal cannot handle it. I don't know what kind of terminal you have, but you need to set properties to be able to handle 10 thousand or even more lines.
Just to understand: we know (reading your last trace) the SIGSEGV occurred in process 8646, but we have no idea how it was started (what is it), because that part is missing.
On MATE terminal and GNOME terminal (It looked like you might be using GNOME or MATE from your screenshots), if you choose edit -> profile preferences, then click on the Scrolling tab. You will see a check box that lets you set your terminal to support an unlimited number of lines.
yes, because your terminal cannot handle it. I don't know what kind of terminal you have, but you need to set properties to be able to handle 10 thousand or even more lines.
Just to understand: we know (reading your last trace) the SIGSEGV occurred in process 8646, but we have no idea how it was started (what is it), because that part is missing.
Quote:
Originally Posted by tyler2016
On MATE terminal and GNOME terminal (It looked like you might be using GNOME or MATE from your screenshots), if you choose edit -> profile preferences, then click on the Scrolling tab. You will see a check box that lets you set your terminal to support an unlimited number of lines.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
