This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Malloc Hanging Multiple Threads
- From: "Douglas Bush" <dbush at extremeeng dot com>
- To: "'Andrew Lunn'" <andrew dot lunn at ascom dot ch>
- Cc: "'eCos Discussion List'" <ecos-discuss at sources dot redhat dot com>
- Date: Mon, 11 Feb 2002 09:17:23 -0700
- Subject: RE: [ECOS] Malloc Hanging Multiple Threads
Thanks for the tip. That will help refine my bug hunt.
I'm actually taking this project over from someone else, so I'm not too
sure about what's been modified. After hunting exhaustively for an
elusive real time bug in our Wavelan device driver, I've come to the
conclusion that the driver works just fine.
-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of Andrew Lunn
Sent: Monday, February 11, 2002 1:24 AM
To: Douglas Bush
Cc: eCos Discussion List
Subject: Re: [ECOS] Malloc Hanging Multiple Threads
On Fri, Feb 08, 2002 at 02:52:18PM -0700, Douglas Bush wrote:
Think about it. Why would the idle thread be in malloc.cxx?
>
/ecos-c/pa/cvs/eCosRepository/ecos/packages/services/memalloc/common/cur
> rent/src/malloc.cxx:166
> * 1 Thread 1 ( Name: Idle Thread, State: running, Priority: 31 )
> idle_thread_main (data=142466)
> at
>
/ecos-c/pa/cvs/eCosRepository/ecos/packages/kernel/current/src/common/th
> r---Type <return> to continue, or q <return> t
> o quit---
My guess is that the image you are executing and the image gdb is
using are not one and the same.
Andrew
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss