From: ronkhu <ronkhu@ntsp.nec.co.jp>
To: qhwang <qhwang@ieeta.pt>, linux-c-programming@vger.kernel.org
Subject: Re: out of memory
Date: Wed, 08 Oct 2003 23:22:40 +0800 [thread overview]
Message-ID: <3F842BC0.6070503@hq.ntsp.nec.co.jp> (raw)
In-Reply-To: 008901c38dad$e7ba22e0$70ab88c1@ieeta.pt
Hello,
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?
-Ron
qhwang wrote:
>Hi, there
>
>Below is the relevant piece of code. The main loop
>
>
> for(i=0;i<(rows-32);i++)
> for(j=0;j<(cols-32);j++) {
> GetSubWindow(image,win,i,j,cols,32,32);
> detectiontest(win, w, tol, nvar,MU,SI,PS,ES,MUT,SIT,PST,EST,32); //the
>statistical learning algo
> ...
> }
>
>in detectiontest
>...
> do
> {
> /* EM algorithm */
> p1=1.0;
> p1*=emhht(w,P,MU,SI,PS,ES);
>
> /* check convergence */
> temp=computeerr(...);
> ...
> }
> while(temp > tol);
>...
>
>There are lot of memory allocation in function emhht but they are well
>conducted. There should be no problem with it.
>
>Any suggestion?
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
next prev parent reply other threads:[~2003-10-08 15:22 UTC|newest]
Thread overview: 10+ 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 [this message]
2003-10-08 16:31 ` qhwang
[not found] ` <1065630558.3f843b5e20715@www.correo.unam.mx>
2003-10-08 16:45 ` qhwang
2003-10-09 11:00 ` qhwang
2003-10-08 12:44 Sandro Dangui
2003-10-08 13:31 ` Mariano Moreyra
2003-10-08 13:38 ` Piyush Jain
-- strict thread matches above, loose matches on Subject: below --
2003-10-08 11:34 qhwang
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=3F842BC0.6070503@hq.ntsp.nec.co.jp \
--to=ronkhu@ntsp.nec.co.jp \
--cc=linux-c-programming@vger.kernel.org \
--cc=qhwang@ieeta.pt \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).