Comment 2 for bug 219294
Revision history for this message
| Matt Fischer (mfisch) wrote Re: xterm segfaults if more than 9999 scroll lines | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
More notes.
1) I ran run this under the same args and sometimes it will fail and sometimes succeed. I am killing the window after each run, so I am not showing hundreds of windows (and so I'm not out of memory).
In this example, you see the same ags and they fail, then work, then fail!
mfisch@tadow:~$ xterm +vb -sb -sl 10001 -bg black -fg red -fn 7x13bold
Segmentation fault
mfisch@tadow:~$ xterm +vb -sb -sl 10001 -bg black -fg red -fn 7x13bold
mfisch@tadow:~$ xterm +vb -sb -sl 10001 -bg black -fg red -fn 7x13bold
Segmentation fault
2) I noticed that this keeps showing up in .xsession-errors when there is an error. Unfortunately, I'm more of a systems programmer (think commandline), so I'm out of my element on what this means:
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x3800010