From: "qhwang" <qhwang@ieeta.pt>
To: ronkhu@ntsp.nec.co.jp
Cc: linux-c-programming@vger.kernel.org
Subject: Re: out of memory
Date: Wed, 8 Oct 2003 17:31:17 +0100 [thread overview]
Message-ID: <00a301c38db9$997edc40$70ab88c1@ieeta.pt> (raw)
In-Reply-To: 3F842BC0.6070503@hq.ntsp.nec.co.jp
> hmmm... how about making use of software tools? like gdb? how about
> other profilers?
> r u sure memory storage had been properly deallocated within emhht?
I have already used gdb for debugging but the problem is still there. In the
function emhht, there are 8 2D pointers to structure allocated and released.
Seven structures have two double type members, 1 has four double type
members. The factual sizes of pointers are 32x32. My computer reports that
the double type is 8 bytes. So, bascially the amount of memory each time
needed is (7*8*2+8*4)*32*32=144 KB. If there structure are not released,
there should be a big mess. But they are really released in my program. And
there is no reportedly illegal memory operation when I set MALLOC_CHECK_=1
for checking.
QingHua
next prev parent reply other threads:[~2003-10-08 16:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31E38B53D182D51195FA00508BE3A33402CE4C9B@zwnbc004.cala.nortel.com>
2003-10-08 12:36 ` out of memory qhwang
2003-10-08 15:07 ` qhwang
2003-10-08 15:22 ` ronkhu
2003-10-08 16:31 ` qhwang [this message]
[not found] ` <1065630558.3f843b5e20715@www.correo.unam.mx>
2003-10-08 16:45 ` qhwang
2003-10-09 11:00 ` qhwang
2006-04-03 10:59 Ingo Freund
2006-04-04 3:40 ` Andrew Morton
2006-04-04 8:31 ` Ingo Freund
2006-04-04 8:54 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-12-23 15:57 Out " Luca Ferrari
2004-12-23 17:08 ` chuck gelm
2003-10-08 12:44 out " Sandro Dangui
2003-10-08 13:31 ` Mariano Moreyra
2003-10-08 13:38 ` Piyush Jain
2003-10-08 11:34 qhwang
2003-02-12 17:29 Balram Adlakha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00a301c38db9$997edc40$70ab88c1@ieeta.pt' \
--to=qhwang@ieeta.pt \
--cc=linux-c-programming@vger.kernel.org \
--cc=ronkhu@ntsp.nec.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.