[openbox] Feh Borderless - Anyone Achieved This In Openbox?

Jim Rees rees at umich.edu
Sun Jul 28 13:26:20 EDT 2013


Brian Mattern wrote:

  On Sun, 28 Jul 2013, Jim Rees wrote:
  
  > Brian Mattern wrote:
  > 
  >   It turns out that it is a genuine bug in feh that is triggered when gcc
  >   optimizations are turned on. (I happened to recompile without
  >   optimization, and thus saw the bug disappear.)
  > 
  > Your fix might work for you, but that's just by accident. You have only
  > filled the first five bytes of a message that's 20 bytes long, and the other
  > 15 bytes are whatever garbage happens to be on the stack.
  
  
  You're right (so much for a quick fix after midnight).
  
  However, it turns out that your fix (simply memsetting mwmhints) *also*
  works just by accident.
  
  The correct fix is attached. On 64-bit machines, X apparently means
  "long" when it says "32", and NOT 32 bits. So, it actually expects 40
  bytes of data to be passed.

That doesn't make sense. Openbox has its own definition of mwmhints, and the
elements are declared as guint, which is an unsigned int. I wonder if
openbox is doing the right thing.

Also I'd be much happier if you left the memset in.


More information about the openbox mailing list