Re: rpmdb segfaults after upgrade from rpm 4.6.0

2009-11-18 Thread Jeff Johnson
On Nov 18, 2009, at 9:15 AM, Per Øyvind Karlsen wrote: > > Hmm, if not automatically handling this in code, what about some option, > macro or something? It obviously seems like something that a lot of people is > likely to run into and therefore should be dealt with in a way easily usable >

Re: rpmdb segfaults after upgrade from rpm 4.6.0

2009-11-18 Thread Per Øyvind Karlsen
2009/11/18 Jeff Johnson > > So what is needed is a --rebuilddb with the PROT_WRITE added, and > then revert to only setting PROT_READ. How you wish to achieve > that conversion on the fly is up to you. The forward looking goal > is to use PROT_READ hardware protection rather than all the > overly

Re: rpmdb segfaults after upgrade from rpm 4.6.0

2009-11-17 Thread Jeff Johnson
On Nov 17, 2009, at 7:56 PM, Per Øyvind Karlsen wrote: > > hmm, I might've misunderstood you..? > I provided you with the rpmdb that I had rebuilt with --rebuilddb, where only > rpm -qa foo\* didn't work.. I should've perhaps provided you the one that > resulted in segfaults with --rebuilddb e

Re: rpmdb segfaults after upgrade from rpm 4.6.0

2009-11-17 Thread Per Øyvind Karlsen
2009/11/18 Jeff Johnson > > On Nov 17, 2009, at 12:49 PM, Per Øyvind Karlsen wrote: > > > D: == DSA pubkey id dd684d7a 26752624 > (h#1) > D: rpmdb: read h# 769 Header V3 DSA signature: OK, key ID > 26752624 > error: rpmdb: damaged header #769 retrieved -- > skipping. > D: rpmdb: read

Re: rpmdb segfaults after upgrade from rpm 4.6.0

2009-11-17 Thread Jeff Johnson
On Nov 17, 2009, at 12:49 PM, Per Øyvind Karlsen wrote: > > D: == DSA pubkey id dd684d7a 26752624 (h#1) > > D: rpmdb: read h# 769 Header V3 DSA signature: OK, key ID 26752624 > > error: rpmdb: damaged header #769 retrieved -- skipping.

Re: rpmdb segfaults after upgrade from rpm 4.6.0

2009-11-17 Thread Per Øyvind Karlsen
2009/11/17 Jeff Johnson > > On Nov 17, 2009, at 12:49 PM, Per Øyvind Karlsen wrote: > > > > 2009/11/17 Jeff Johnson > >> >> On Nov 17, 2009, at 12:40 PM, Per Øyvind Karlsen wrote: >> >> > I just did a fresh install of Mandriva Linux and updated to rpm 5.2 now, >> > and this happens: >> > >> >> Y

Re: rpmdb segfaults after upgrade from rpm 4.6.0

2009-11-17 Thread Jeff Johnson
On Nov 17, 2009, at 12:49 PM, Per Øyvind Karlsen wrote: > > > 2009/11/17 Jeff Johnson > > On Nov 17, 2009, at 12:40 PM, Per Øyvind Karlsen wrote: > > > I just did a fresh install of Mandriva Linux and updated to rpm 5.2 now, > > and this happens: > > > > Yup. Attached patch avoids the segfa

Re: rpmdb segfaults after upgrade from rpm 4.6.0

2009-11-17 Thread Per Øyvind Karlsen
2009/11/17 Jeff Johnson > > On Nov 17, 2009, at 12:40 PM, Per Øyvind Karlsen wrote: > > > I just did a fresh install of Mandriva Linux and updated to rpm 5.2 now, > > and this happens: > > > > Yup. Attached patch avoids the segfault: > > Index: rpmdb/header_internal.c > ==

Re: rpmdb segfaults after upgrade from rpm 4.6.0

2009-11-17 Thread Jeff Johnson
On Nov 17, 2009, at 12:40 PM, Per Øyvind Karlsen wrote: > I just did a fresh install of Mandriva Linux and updated to rpm 5.2 now, > and this happens: > Yup. Attached patch avoids the segfault: Index: rpmdb/header_internal.c === R

rpmdb segfaults after upgrade from rpm 4.6.0

2009-11-17 Thread Per Øyvind Karlsen
I just did a fresh install of Mandriva Linux and updated to rpm 5.2 now, and this happens: [r...@localhost rpm]# valgrind rpm --rebuilddb -vvv --rpmdbdebug ==23457== Memcheck, a memory error detector ==23457== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==23457== Using Valgrind