Menu

#266 terminate called after throwing an instance of 'std::bad_all

need info
open
nobody
httools (7)
5
2014-08-22
2005-09-15
Anonymous
No

Peter: Reply-To: athleston@yahoo.com
htdig version: 3.2.0.0-8 (mdk naming scheme)
OS: Mandriva Linux LE 2005
KDE version: 3.3.2

I get the following error trace with rundig on the CLI:

[root@client peter]# /usr/bin/rundig
terminate called after throwing an instance of
'std::bad_alloc'
what(): St9bad_alloc
/usr/bin/rundig: line 48: 32293 Aborted
$BINDIR/htnotify $opts
---------------------------------------------------------------------------------------------------------------------

My posix root account/email log shows a series of such
failures occurring over a period of time (verbose,
verbatim) :

From root@EdinaOffice.com Fri Sep 9 05:24:49 2005
Return-Path: <root@EdinaOffice.com>
X-Original-To: root
Delivered-To: postfix@client.EdinaOffice.com
Received: by client.EdinaOffice.com (Postfix, from
userid 0)
id A29E678D; Fri, 9 Sep 2005 05:24:49 -0500 (CDT)
From: root@EdinaOffice.com (Cron Daemon)
To: root@EdinaOffice.com
Subject: Cron <root@client> nice -n 19 run-parts
/etc/cron.daily
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/>
X-Cron-Env: <LOGNAME=root>
Message-Id:
<20050909102449.A29E678D@client.EdinaOffice.com>
Date: Fri, 9 Sep 2005 05:24:49 -0500 (CDT)

terminate called after throwing an instance of
'std::bad_alloc'
what(): St9bad_alloc
/usr/bin/rundig: line 48: 24141 Aborted
$BINDIR/htnotify $opts

From root@EdinaOffice.com Sat Sep 10 04:25:44 2005
Return-Path: <root@EdinaOffice.com>
X-Original-To: root
Delivered-To: postfix@client.EdinaOffice.com
Received: by client.EdinaOffice.com (Postfix, from
userid 0)
id 43202279; Sat, 10 Sep 2005 04:25:44 -0500 (CDT)
From: root@EdinaOffice.com (Cron Daemon)
To: root@EdinaOffice.com
Subject: Cron <root@client> nice -n 19 run-parts
/etc/cron.daily
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/>
X-Cron-Env: <LOGNAME=root>
Message-Id:
<20050910092544.43202279@client.EdinaOffice.com>
Date: Sat, 10 Sep 2005 04:25:44 -0500 (CDT)

terminate called after throwing an instance of
'std::bad_alloc'
what(): St9bad_alloc
/usr/bin/rundig: line 48: 22211 Aborted
$BINDIR/htnotify $opts

From root@EdinaOffice.com Sun Sep 11 04:37:19 2005
Return-Path: <root@EdinaOffice.com>
X-Original-To: root
Delivered-To: postfix@client.EdinaOffice.com
Received: by client.EdinaOffice.com (Postfix, from
userid 0)
id BD93A889; Sun, 11 Sep 2005 04:37:18 -0500 (CDT)
From: root@EdinaOffice.com (Cron Daemon)
To: root@EdinaOffice.com
Subject: Cron <root@client> nice -n 19 run-parts
/etc/cron.daily
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/>
X-Cron-Env: <LOGNAME=root>
Message-Id:
<20050911093718.BD93A889@client.EdinaOffice.com>
Date: Sun, 11 Sep 2005 04:37:18 -0500 (CDT)

terminate called after throwing an instance of
'std::bad_alloc'
what(): St9bad_alloc
/usr/bin/rundig: line 48: 28015 Aborted
$BINDIR/htnotify $opts

From root@EdinaOffice.com Mon Sep 12 04:21:45 2005
Return-Path: <root@EdinaOffice.com>
X-Original-To: root
Delivered-To: postfix@client.EdinaOffice.com
Received: by client.EdinaOffice.com (Postfix, from
userid 0)
id CBBCD2A1; Mon, 12 Sep 2005 04:21:45 -0500 (CDT)
From: root@EdinaOffice.com (Cron Daemon)
To: root@EdinaOffice.com
Subject: Cron <root@client> nice -n 19 run-parts
/etc/cron.daily
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/>
X-Cron-Env: <LOGNAME=root>
Message-Id:
<20050912092145.CBBCD2A1@client.EdinaOffice.com>
Date: Mon, 12 Sep 2005 04:21:45 -0500 (CDT)

terminate called after throwing an instance of
'std::bad_alloc'
what(): St9bad_alloc
/usr/bin/rundig: line 48: 24494 Aborted
$BINDIR/htnotify $opts

From root@EdinaOffice.com Tue Sep 13 04:22:04 2005
Return-Path: <root@EdinaOffice.com>
X-Original-To: root
Delivered-To: postfix@client.EdinaOffice.com
Received: by client.EdinaOffice.com (Postfix, from
userid 0)
id 89C102BE; Tue, 13 Sep 2005 04:22:04 -0500 (CDT)
From: root@EdinaOffice.com (Cron Daemon)
To: root@EdinaOffice.com
Subject: Cron <root@client> nice -n 19 run-parts
/etc/cron.daily
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/>
X-Cron-Env: <LOGNAME=root>
Message-Id:
<20050913092204.89C102BE@client.EdinaOffice.com>
Date: Tue, 13 Sep 2005 04:22:04 -0500 (CDT)

terminate called after throwing an instance of
'std::bad_alloc'
what(): St9bad_alloc
/usr/bin/rundig: line 48: 24047 Aborted
$BINDIR/htnotify $opts

From root@EdinaOffice.com Wed Sep 14 18:06:31 2005
Return-Path: <root@EdinaOffice.com>
X-Original-To: root
Delivered-To: postfix@client.EdinaOffice.com
Received: by client.EdinaOffice.com (Postfix, from
userid 0)
id 27D39254; Wed, 14 Sep 2005 18:06:20 -0500 (CDT)
From: root@EdinaOffice.com (Cron Daemon)
To: root@EdinaOffice.com
Subject: Cron <root@client> nice -n 19 run-parts
/etc/cron.daily
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/>
X-Cron-Env: <LOGNAME=root>
Message-Id:
<20050914230620.27D39254@client.EdinaOffice.com>
Date: Wed, 14 Sep 2005 18:06:20 -0500 (CDT)

terminate called after throwing an instance of
'std::bad_alloc'
what(): St9bad_alloc
/usr/bin/rundig: line 48: 30010 Aborted
$BINDIR/htnotify $opts

Discussion

  • Gilles Detillieux

    • labels: 105979 --> httools
     
  • Gilles Detillieux

    Logged In: YES
    user_id=149687

    Based on what you describe, it sounds like Mandriva is including
    an older release of the 3.2 betas than what's current (3.2.0b6,
    which has been out since June 16, 2004). The question is, how
    old? If it's a 3.2.0b4 pre-release from before Aug 9, 2002, that
    would explain the bug in htnotify. If it's newer than that, then I'm at
    a bit of a loss to explain the error. Try running "htnotify -\?" to see
    what version number it reports. Let us know if it reports something
    we can use. The Mandriva package's version number is somewhat
    meaningless to us as it doesn't tell us which 3.2.0 beta release it's
    based on (i.e. b3, b4 snapshots, b5 or b6).

    In any case, given that htnotify doesn't appear on line 48 of rundig
    anymore in our release, it's pretty safe to say Mandriva isn't using
    the latest 3.2.0b6 release, so you should request that they do. It
    contains a lot of fixes for bugs in older beta releases.

    If they don't help you by providing an updated package, and if
    you're not using htnotify anyway, you can just comment out that
    command on line 48 of your current /usr/bin/rundig script.

     
  • Gilles Detillieux

    • milestone: --> need info
     

Log in to post a comment.

Monday.com Logo