From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12370 invoked by alias); 1 Oct 2013 15:27:53 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 12355 invoked by uid 89); 1 Oct 2013 15:27:53 -0000 Received: from p02c11o143.mxlogic.net (HELO p02c11o143.mxlogic.net) (208.65.144.76) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 01 Oct 2013 15:27:53 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.3.2 X-HELO: p02c11o143.mxlogic.net Received: from unknown [12.218.215.72] (EHLO smtpauth1.linear.com) by p02c11o143.mxlogic.net(mxl_mta-7.1.0-4) with ESMTP id 4f9ea425.0.27826.00-306.73330.p02c11o143.mxlogic.net (envelope-from ); Tue, 01 Oct 2013 09:27:52 -0600 (MDT) X-MXL-Hash: 524ae9f8643f1313-b3435335b074700d7bc28eb33257d5e336400608 Received: from colorado-as3.engineering.linear.com (unknown [10.186.3.62]) by smtpauth1.linear.com (Postfix) with ESMTPSA id F1704740AB; Tue, 1 Oct 2013 08:27:46 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Michael Jones In-Reply-To: <1380618091882-245807.post@n7.nabble.com> Date: Tue, 01 Oct 2013 15:27:00 -0000 Cc: ecos-discuss@ecos.sourceware.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <1380618091882-245807.post@n7.nabble.com> To: Daniel Zebralla X-AnalysisOut: [v=2.0 cv=c/Uct2Bl c=1 sm=1 a=glloKNylpeYNumXQcclYyA==:17 a] X-AnalysisOut: [=UPQHJqM1TLwA:10 a=D2_GN2MmYMYA:10 a=BLceEmwcHowA:10 a=kj9] X-AnalysisOut: [zAlcOel0A:10 a=MqDINYqSAAAA:8 a=uy2HWQom_qQA:10 a=9I5xiGou] X-AnalysisOut: [AAAA:8 a=CCpqsmhAAAAA:8 a=EVGuTxpmaRLsUQCaopUA:9 a=CjuIK1q] X-AnalysisOut: [_8ugA:10 a=HGfe06VmjFAA:10 a=2fPOlPt4dusA:10 a=vUm5aIvg_Ms] X-AnalysisOut: [A:10] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)] X-MAIL-FROM: X-IsSubscribed: yes Subject: Re: [ECOS] Typo in assert error message causing confusion? X-SW-Source: 2013-10/txt/msg00001.txt.bz2 Daniel, I think it is printing the assertion, not the failure. It would be clearer if it printed: Assertion "data pointer NNN is valid" failed But it might be consistent with standard practice. I am not sure. Mike On Oct 1, 2013, at 3:01 AM, Daniel Zebralla wrote: >> From /host/infra/cyg_ass.h as well as /host/infra/cyg/infra/cyg_ass.h: >=20 > # define CYG_CHECK_DATA_PTRC( _ptr_ ) \ > CYG_MACRO_START \ > if ( !cyg_check_data_ptr((void *)(_ptr_))) \ > CYG_ASSERT_DOCALL("data pointer (" #_ptr_ ") is valid");\ > CYG_MACRO_END >=20 > # define CYG_CHECK_FUNC_PTRC( _ptr_ ) \ > CYG_MACRO_START \ > if ( !cyg_check_func_ptr((void (*)(void))(_ptr_))) \ > CYG_ASSERT_DOCALL("function pointer (" #_ptr_ ") is valid"); \ > CYG_MACRO_END >=20 > As I understand, CYG_ASSERT_DOCALL is triggered when the checked data or > function pointer is invalid. The printed message however indicates that t= he > checked pointer is valid. Is this an error or am I misunderstanding the > usage of CYG_ASSERT_DOCALL here? >=20 > Thanks for clarification! >=20 >=20 >=20 > -- > View this message in context: http://sourceware-org.1504.n7.nabble.com/Ty= po-in-assert-error-message-causing-confusion-tp245807.html > Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.co= m. >=20 > --=20 > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss >=20 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss