On Sat, 2017-06-10 at 10:07 -0700, Samuel Sieb wrote: > On 06/10/2017 02:42 AM, Patrick O'Callaghan wrote: > > On running 'dnf update' this morning I got a segfault from > > /usr/lib/libdb-5.3.so, which is part of libdb-5.3.28-21.fc25, so the > > problem is more than just an incompatible database. > > > > However removing the temp files and rebuilding the db seems to have > > cleared it. > > Don't those two paragraphs contradict each other? You rebuilt the > database and there's no more segfault. The problem is that a certain > structure from glibc that is stored in the database has changed it's > format. Clearing the temp files removes that structure so after that > there's no problem. My point is that an incompatibility in a database should never cause a segfault under any circumstances. If it happens it means the db library is not adequately testing its input. This kind of thing is what leads to security holes as well as broken software. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
