BOUNCE rtl@rtlinux.org: Approval required: (fwd)

[Der Herr Hofrat <der.herr@hofr.at>]

>From owner-rtl Tue Jul 17 03:07:22 2001
Received: from gw-nl4.philips.com (gw-nl4.philips.com [212.153.190.6])
	by localhost.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f6H97LU15449
	for <rtl@fsmlabs.com>; Tue, 17 Jul 2001 03:07:21 -0600
Received: from smtpscan-nl2.philips.com (localhost.philips.com [127.0.0.1])
          by gw-nl4.philips.com with ESMTP id LAA26014
          for <rtl@fsmlabs.com>; Tue, 17 Jul 2001 11:06:37 +0200 (MEST)
          (envelope-from w.wardenaar@philips.com)
From: w.wardenaar@philips.com
Received: from smtpscan-nl2.philips.com(130.139.36.22) by gw-nl4.philips.com via mwrap (4.0a)
	id xma026012; Tue, 17 Jul 01 11:06:37 +0200
Received: from smtprelay-nl1.philips.com (localhost [127.0.0.1]) 
	by smtpscan-nl2.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id LAA16771
	for <rtl@fsmlabs.com>; Tue, 17 Jul 2001 11:06:34 +0200 (MET DST)
Received: from notessmtp-nl1.philips.com (notessmtp-nl1.philips.com [130.139.36.10]) 
	by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id LAA09178
	for <rtl@fsmlabs.com>; Tue, 17 Jul 2001 11:06:34 +0200 (MET DST)
Received: from EHAUO01.diamond.philips.com (ehauo01sv1.diamond.philips.com [130.139.54.215]) 
	by notessmtp-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id LAA22999
	for <rtl@fsmlabs.com>; Tue, 17 Jul 2001 11:06:28 +0200 (MET DST)
Subject: Re: [rtl] Using debug_module, what is exception 0xe? -> Memory allocation
 in C++.
To: rtl@fsmlabs.com
Date: Tue, 17 Jul 2001 11:03:40 +0200
Message-ID: <OF8499F3C6.2559289B-ONC1256A8C.00305519@diamond.philips.com>
X-MIMETrack: Serialize by Router on EHAUO01/H/SERVER/PHILIPS(Release 5.0.5 |September 22, 2000) at
 17/07/2001 11:07:32
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii


Dear Michael,

> Exception 0xe is a page fault. The likely reason is that
> rtlcpp's "new" calls kmalloc which is not allowed in a RT-thread context.

Could there be a typo in your reaction?
If not, how could I allocate memory in RT-thread context?
Or should I only use kmalloc in init_module?
I am working with an application, using an "object factory" in
a kernel space thread and our first impression is that it is working.
Since your attitude towards C++ seems to be changing (:-)), I hope to
get a constuctive reply for you.

Greetings, Willem Wardenaar
Philips, CFT, E&T, MCT

----- End of forwarded message from owner-rtl@fsmlabs.com -----