← Back to team overview

mythbuntu-bugs team mailing list archive

[Bug 302266] Re: lircd segfaults on startup with large codes in lircd.conf

 

This is fixed, at least in last version 0.9.4c

** Changed in: lirc (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/302266

Title:
  lircd segfaults on startup with large codes in lircd.conf

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lirc

  (This might be related to
  https://bugs.launchpad.net/mythbuntu/+bug/222250)

  The Hauppauge PVR-150 raw codes can be quite large.  It appears that
  if you have a code in your lircd.conf file that is >= 2^31, you will
  get a segfault starting lircd.  The codes I need to use for my
  satellite receiver start at 2156396544 (>8 million larger than 2^31
  :).

  If I have a lircd.conf like this (note the raw code is (2^31)-1):

  --------------
  begin remote
          name blaster
                  bits 32
                  flags RAW_CODES
                  eps 0
                  aeps 0
                  plead 0
                  gap 333333
                  repeat_bit 0
                  begin raw_codes
                      name 0
                      2147483647
                  end raw_codes
  end remote
  ----------------

  lircd will start.  However, if I use (note the raw-code has increased
  by one to 2^31):

  -----------------
  begin remote
          name blaster
                  bits 32
                  flags RAW_CODES
                  eps 0
                  aeps 0
                  plead 0
                  gap 333333
                  repeat_bit 0
                  begin raw_codes
                      name 0
                      2147483648
                  end raw_codes
  end remote
  -------------

  I get a segfault starting lircd.

  I've tried changing "bits" to be a larger number, but it does not seem
  to be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/302266/+subscriptions