Hi, Marc. Thanks for the reply. I downloaded the 9.22 source code and added -ggdb to src/Makefile's CXXFLAGS (I didn't remove -g). I configured with ./configure --disable-perl since it wouldn't configure with perl. Then I ran "make".
I determined that if I run xrdb xres && src/rxvt Where xres is a file containing "rxvt.saveLines: 1048576" I got this backtrace: ryantm@ryantm-1604 ~/p/rxvt-unicode-9.22 (master)$ xrdb xres && gdb src/rxvt GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from src/rxvt...done. (gdb) run Starting program: /home/ryantm/p/rxvt-unicode-9.22/src/rxvt Program received signal SIGSEGV, Segmentation fault. rxvt_term::scr_alloc (this=this@entry=0x722040) at screen.C:193 193 l.t = (text_t *)base; base += tsize; (gdb) backtrace #0 rxvt_term::scr_alloc (this=this@entry=0x722040) at screen.C:193 #1 0x000000000040761b in rxvt_term::scr_reset (this=this@entry=0x722040) at screen.C:256 #2 0x00000000004090ce in rxvt_term::scr_poweron (this=this@entry=0x722040) at screen.C:468 #3 0x0000000000418256 in rxvt_term::init2 (this=this@entry=0x722040, argc=argc@entry=1, argv=argv@entry=0x7fffffffd408) at init.C:818 #4 0x00000000004183f5 in rxvt_term::init (this=this@entry=0x722040, argc=argc@entry=1, argv=argv@entry=0x7fffffffd408, envv=<optimized out>) at init.C:780 #5 0x0000000000409d8c in main (argc=1, argv=0x7fffffffd408) at rxvt.C:37 I noted that if I changed the saveLines number to the maximum number in the manual "65535" it did not segmentation fault. This problem seems intermittent, because VirtualBox froze on me and when I saved the VM and restarted it, the problem is not reproducing. Unfortunately, that means I couldn't figure out exactly what numerical boundary was causing the segmentation fault. I hope this is helpful. Please let me know if there is anything else I can do. Ryan On Mon, Jul 10, 2017 at 12:47 PM Marc Lehmann <[email protected]> wrote: > On Mon, Jul 10, 2017 at 04:10:58PM +0000, Ryan Mulligan <[email protected]> > wrote: > > I am running rxvt-unicode inside VirtualBox with a Windows 10 host and a > > Ubuntu 16.04 guest. My window system has gotten into a state where when I > > launch urxvt and maximize it, it segfaults. > > Hi, and thanks for your report! > > Could you recompile with debug info (e.g. -ggdb), and, ifpoossible, the > current evrsion (9.22) and make the backtrace again? That would be helpful > as > your current backtrace shows no variables or line numbers. > > Thanks! > > -- > The choice of a Deliantra, the free code+content > MORPG > -----==- _GNU_ http://www.deliantra.net > ----==-- _ generation > ---==---(_)__ __ ____ __ Marc Lehmann > --==---/ / _ \/ // /\ \/ / [email protected] > -=====/_/_//_/\_,_/ /_/\_\ >
_______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/mailman/listinfo/rxvt-unicode
