[Nut-upsdev] Newhidups gets unbound after a while

[Peter Selinger]

I believe this is the bug that was fixed in r392 (April 5):

----------------------------------------------------------------------
r392 | aquette | 2006-04-05 05:04:37 -0300 (Wed, 05 Apr 2006) | 3 lines

newhidups: fix the "double free or corruption" crash upon device
   reconnexion (Debian bug #354305)
----------------------------------------------------------------------

However, the fix is a bit of cheating, because the device data
structure now simply isn't freed at all.  I would still like to find
out what caused this "double free" problem. I spent a few hours
reading the libusb sources, and I could not find any memory management
code that was suspicious.  Very unsatisfying. It works for now, but I
think I will try to scrutinize this bug a little more when I have
time, particularly since I think it did not occur before December or
so. -- Peter

Arnaud Quette wrote:
> 
> [back from a short week of holidays, just quickly passing by...]
> 
> salut Patrick et all,
> 
> 2006/5/2, Patrick Agrain <patrick.agrain at alcatel.fr>:
> > ...
> > ==================================================
> > = device has been disconnected, try to reconnect =
> > ==================================================
> > Closing device
> > Reopening device
> > Segmentation fault
> 
> if this segfault isn't due to some badly handled ctrl+c, then this is
> a known bug (ie
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354305)
> 
> I still have to find a bit of time for releasing 2.0.4.
> 
> Arnaud
> 
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
>