From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12771 invoked by alias); 11 Jul 2002 21:18:05 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 12764 invoked from network); 11 Jul 2002 21:18:05 -0000 Received: from unknown (HELO hermes.chez-thomas.org) (63.225.98.241) by sources.redhat.com with SMTP; 11 Jul 2002 21:18:05 -0000 Received: from localhost.localdomain (localhost [127.0.0.1]) by hermes.chez-thomas.org (Postfix) with ESMTP id 3466C138F; Thu, 11 Jul 2002 15:18:04 -0600 (MDT) From: Gary Thomas To: George Sosnowski Cc: eCos Discussion In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 11 Jul 2002 14:18:00 -0000 Message-Id: <1026422284.27291.7214.camel@hermes.chez-thomas.org> Mime-Version: 1.0 Subject: Re: [ECOS] malloc/new in DSRs X-SW-Source: 2002-07/txt/msg00167.txt.bz2 On Thu, 2002-07-11 at 15:04, George Sosnowski wrote: > If malloc is configed to be threadsafe in ecos.ecc, then is it ok to use > malloc/new/free/delete in DSRs? > I assume it is, but want to make sure. I would not think so. DSR's are not allowed to "block" and if you got into the DSR while inside some thread-safe protected code (i.e. protected by a semaphore or mutex), it might try to. Calling malloc() and friends from DSR code is normally considered poor practice anyway. Why would you think you need to? -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss