From: Balasaravanan P <pbalasaravanan@gmail.com>
To: Balasaravanan P <pbalasaravanan@gmail.com>,
ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Using standard malloc()
Date: Thu, 12 May 2005 10:59:00 -0000 [thread overview]
Message-ID: <122f850005051122081daf5e71@mail.gmail.com> (raw)
In-Reply-To: <20050511204245.GX31731@lunn.ch>
Hi Andrew,
Thanks for the reply.
I am using MIPS 4kc processor.
I also tried enabling "CYGBLD_ISO_MALLOC_HEADER" but could give correct value.
I have pasted the ecosconfig export ecm file below.
=========================================
cdl_savefile_version 1;
cdl_savefile_command cdl_savefile_version {};
cdl_savefile_command cdl_savefile_command {};
cdl_savefile_command cdl_configuration { description hardware template
package };
cdl_savefile_command cdl_package { value_source user_value
wizard_value inferred_value };
cdl_savefile_command cdl_component { value_source user_value
wizard_value inferred_value };
cdl_savefile_command cdl_option { value_source user_value wizard_value
inferred_value };
cdl_savefile_command cdl_interface { value_source user_value
wizard_value inferred_value };
cdl_configuration eCos {
description "" ;
hardware mips32_4kc ;
template kernel ;
package -hardware CYGPKG_HAL_MIPS v2_0 ;
package -hardware CYGPKG_HAL_MIPS_MIPS32 v2_0 ;
package -hardware CYGPKG_HAL_MIPS v2_0 ;
package CYGPKG_HAL v2_0 ;
package CYGPKG_IO v2_0 ;
package CYGPKG_IO_SERIAL v2_0 ;
package CYGPKG_INFRA v2_0 ;
package CYGPKG_KERNEL v2_0 ;
package CYGPKG_ERROR v2_0 ;
package CYGPKG_MEMALLOC v2_0 ;
package CYGPKG_ISOINFRA v2_0 ;
};
cdl_option CYGFUN_HAL_COMMON_KERNEL_SUPPORT {
user_value 1
};
cdl_option CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK {
user_value 0
};
cdl_option CYGHWR_HAL_MIPS_MIPS32_CORE {
user_value 4Kc
};
cdl_component CYGSEM_KERNEL_SCHED_TIMESLICE {
user_value 1
};
cdl_component CYGPKG_KERNEL_INSTRUMENT {
user_value 0
};
cdl_option CYGDBG_KERNEL_INSTRUMENT_SMP {
user_value 0
};
cdl_component CYGDBG_KERNEL_INSTRUMENT_MSGS {
user_value 0
};
cdl_option CYGSEM_MEMALLOC_ALLOCATOR_FIXED_THREADAWARE {
user_value 0
};
cdl_option CYGSEM_MEMALLOC_ALLOCATOR_VARIABLE_THREADAWARE {
user_value 0
};
cdl_option CYGSEM_MEMALLOC_ALLOCATOR_VARIABLE_COALESCE {
user_value 0
};
cdl_option CYGBLD_MEMALLOC_MALLOC_IMPLEMENTATION_HEADER {
user_value <cyg/memalloc/dlmalloc.hxx>
};
cdl_option CYGIMP_MEMALLOC_MALLOC_VARIABLE_SIMPLE {
user_value 0
};
cdl_option CYGIMP_MEMALLOC_MALLOC_DLMALLOC {
user_value 1
};
cdl_option CYGBLD_ISO_ERRNO_CODES_HEADER {
inferred_value 1 <cyg/error/codes.h>
};
cdl_option CYGBLD_ISO_ERRNO_HEADER {
inferred_value 1 <cyg/error/errno.h>
};
cdl_option CYGBLD_ISO_RAND_HEADER {
user_value 0 0
};
cdl_option CYGBLD_ISO_MALLOC_HEADER {
user_value 0 0
};
cdl_option CYGBLD_ISO_STDLIB_SYSTEM_HEADER {
user_value 0 0
};
cdl_option CYGBLD_ISO_STRERROR_HEADER {
inferred_value 1 <cyg/error/strerror.h>
};
Best Regards,
Bala.
On 5/12/05, Andrew Lunn <andrew@lunn.ch> wrote:
> On Wed, May 11, 2005 at 11:34:30AM +0530, Balasaravanan P wrote:
> > Hi,
> >
> > I am writing an abstraction layer for an existing application this
> > requires me to use malloc to create threads.
> >
> > I tried using the standard LIBC malloc which returns NULL. I tried
> > printing the mallinfo structure and it shows 0 for all its members.
> >
> > Is there any other way to use standard malloc or am I missing any
> > configuration steps.
>
> You are missing something somewhere. malloc should work. What is the
> target and the configuration? Do an ecosconfig export and post the
> result.
>
> Andrew
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-05-12 5:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 8:53 Balasaravanan P
2005-05-12 5:08 ` Andrew Lunn
2005-05-12 10:59 ` Balasaravanan P [this message]
2005-05-19 10:57 ` Balasaravanan P
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=122f850005051122081daf5e71@mail.gmail.com \
--to=pbalasaravanan@gmail.com \
--cc=ecos-discuss@sources.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).