From: "wangwei" <wangw@start.com.cn>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] help in tcp/ip stack !!!
Date: Thu, 07 Jun 2001 21:00:00 -0000 [thread overview]
Message-ID: <003301c0efce$943e82c0$592da8c0@start.com.cn> (raw)
In-Reply-To: <3B1E3414.D65594C4@redhat.com>
Hi, Jonathan:
I trace it , and find a strange thing .
Before the memory exception happen , there are not any threads in the thread
queue ,system is runing a thread which not exist . I trace the variable
"queue_map", and find :
before that , system put idle thread to sleep and give zero to
"queue_map", and make NONE thread in the
running queue .
At that time , I just connected one tcp to ecos , and the function
cyg_thread_delete hadn't run,ecos application is just doing write(),send
something through tcp . So I'm sure that the exception is not caused by the
application .
I think you maybe met this before , when you disigned ecos . because there
are many assertions about queue_map in the source code of mlqueue.cxx.
Can you give me some advice .It 's very important to me.
thinks.
Best regard .
----- Original Message -----
From: "Jonathan Larmour" <jlarmour@redhat.com>
To: "wangwei" <wangw@start.com.cn>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Wednesday, June 06, 2001 9:45 PM
Subject: Re: [ECOS] help in tcp/ip stack !!!
> wangwei wrote:
> >
> > Thank you ,Jonathan:
> >
> > I try the method you told me, but the except still happened ,
> > and sometimes I got the error of "out of mbuf" .
> > I suspect when many client connected the server,it will write much data
> > by tcp , and it will occupy too much mbuf , and cause "exh 4" when the
> > mbuffer is exhausted .
>
> It looks like you'll have to track down where the exception happened. You
> should probably be able to install a signal handler for the exception in
> question (likely a SEGV or BUS). If you look at the sival_ptr of the
> siginfo_t, that will contain a pointer to the registers, in
> Hal_SavedRegisters format. Or set a breakpoint on
> cyg_posix_exception_handler and look at the exception_info argument which
> is also a pointer to Hal_SavedRegisters.
>
> From that you can determine the PC and possibly also what happened.
>
> Jifl
> --
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
> Come to the Red Hat TechWorld open source conference in Brussels!
> Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/
next prev parent reply other threads:[~2001-06-07 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 18:07 wangwei
2001-06-05 5:53 ` Jonathan Larmour
2001-06-06 3:34 ` wangwei
2001-06-06 6:46 ` Jonathan Larmour
2001-06-07 21:00 ` wangwei [this message]
2001-06-07 21:14 ` Jonathan Larmour
2001-06-10 17:41 ` wangwei
2001-06-11 12:55 ` Jonathan Larmour
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='003301c0efce$943e82c0$592da8c0@start.com.cn' \
--to=wangw@start.com.cn \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).