From: Andrew Lunn <andrew@lunn.ch>
To: Alexander Neundorf <a.neundorf-work@gmx.net>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] "new" heap allocation for synthetic target doesn't work for me
Date: Wed, 11 Jul 2007 13:02:00 -0000 [thread overview]
Message-ID: <20070711130218.GA15344@lunn.ch> (raw)
In-Reply-To: <200707110855.00485.a.neundorf-work@gmx.net>
On Wed, Jul 11, 2007 at 08:55:00AM -0400, Alexander Neundorf wrote:
> Hi,
>
> the "new" (ok, already 1 1/2 years old) way to allocate the memory for the
> heap doesn't work for me (kubuntu 6.10, gcc 4.1.2), i.e. malloc() fails with
> a SIGSEGV in dlmalloc.cxx, line 1282. Reverting this change:
> http://ecos.sourceware.org/cgi-bin/cvsweb.cgi/ecos/packages/hal/synth/arch/current/src/synth_entry.c.diff?r1=1.6&r2=1.7&cvsroot=ecos&f=h
>
> makes it work again.
Do we know what makes the difference. Is it gcc, binutils, kernel?
We need some way to decide at runtime if we need to brk() memory or
not.
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:[~2007-07-11 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 12:55 Alexander Neundorf
2007-07-11 13:02 ` Andrew Lunn [this message]
2007-07-11 15:41 ` Alexander Neundorf
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=20070711130218.GA15344@lunn.ch \
--to=andrew@lunn.ch \
--cc=a.neundorf-work@gmx.net \
--cc=ecos-discuss@sourceware.org \
/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).