On Sun, Aug 14, 2016 at 06:16:11PM +0200, Alessandro DE LAURENZIS wrote: > Mike, > > On Fri, 12 Aug 2016 19:47:40 +0200 > Alessandro DE LAURENZIS <[email protected]> wrote: > > > Hi Mike, > > > > On 2016-08-12 18:54, Mike Larkin wrote: > > > Shrug. Works fine here on i386 and amd64. > > > > > > Do other processes crash as well? What if you leave fluxbox > > > running? Does > > > it eventually fail on its own without needing fluxbox-remote to > > > trigger it? > > > > As far as I can say, no other crash, neither fluxbox nor other > > processes (I'm currently running this session since several hours > > without any > > issues). > > > > Only the restart seems to trigger the misbehaviour. > > Playing with gdb: > > [....................snip....................] > GNU gdb 6.3 > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-unknown-openbsd6.0"...(no debugging symbols > found) > > (gdb) run > Starting program: /usr/local/bin/fluxbox > (no debugging symbols found) > > Program received signal SIGTRAP, Trace/breakpoint trap. > Cannot remove breakpoints because program is no longer writable. > It might be running in another process. > Further execution is probably impossible. > 0x0000173fb63002b0 in ?? () > (gdb) quit > The program is running. Exit anyway? (y or n) > [....................snip....................] > > Does it suggest anything useful? >
No. > -- > Alessandro DE LAURENZIS > [mailto:[email protected]] > LinkedIn: http://it.linkedin.com/in/delaurenzis
