On Wed, 2005-07-06 at 12:17 +0200, Enrico Zini wrote: > On Tue, Jul 05, 2005 at 02:04:38PM -0700, Ross Boylan wrote: > > > Package: debtags > > Version: 0.99.4 > > Severity: normal > > # debtags update > > Get:1 http://people.debian.org/~enrico/tags/tags-current.gz [139kB] > > Get:2 http://people.debian.org/~enrico/tags/vocabulary.gz [7598B] > > Fetched 147kB in 0s (231kB/s) > > Reading tag data and vocabulary for > > http://people.debian.org/~enrico/tags/... > > Writing system vocabulary... > > Writing merged tag database... > > Segmentation fault > > I'm not sure when this started; it used to work. > > May warrant higher severity if this is not some quirk of my system. > > uhm... strange. > > Is that reproductible? That is, does it segfault every time you run > debtags update? > It was reproducible, but now it isn't! It works fine now. Also, I have another, very similar, box, and it never had a problem.
I may have done an aptitude update since the original problems; otherwise, I can't think what would be different--unless the external data has changed. Other possibly relevant info: the system is dual processor Athlon. The original problem appeared while running a weekly cron job (that is, the debtags update was part of the cron job). The cron job from the preceding week ran without incident. > In that case, could you run it under GDB for me? It's like this: > > gdb --args debtags update > I thought gdb wasn't so useful without a debug version of the program. Is that impression incorrect? Since the problem seems to have gone away, you may want to close this bug. Or you could see if anyone else (including me) runs into it again.... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
