From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2568 invoked by alias); 2 Oct 2013 11:26:15 -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 2553 invoked by uid 89); 2 Oct 2013 11:26:14 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 02 Oct 2013 11:26:14 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: sam.nabble.com Received: from tom.nabble.com ([192.168.236.105]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VRKZH-0004hc-B4 for ecos-discuss@ecos.sourceware.org; Wed, 02 Oct 2013 04:26:11 -0700 Date: Wed, 02 Oct 2013 11:26:00 -0000 From: Daniel Zebralla To: ecos-discuss@ecos.sourceware.org Message-ID: <1380713171328-245957.post@n7.nabble.com> In-Reply-To: References: <1380618091882-245807.post@n7.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [ECOS] Re: Typo in assert error message causing confusion? X-SW-Source: 2013-10/txt/msg00002.txt.bz2 I get your point of view. However, I assume that someone would like to know what's broken instead of what would be the case if the message would have not been displayed. If my system stops with a kernel panic and tells me "Pointer is valid" I would be like -> oO. As I can see inside eCos source, I'm not the only one understanding those assertion messages this way, some examples: CYG_ASSERT( freeret , "Couldn't free!" ); CYG_ASSERT( interr == 0, "internal lock failed!" ); CYG_ASSERT( usertmp->next != NULL, "Couldn't find message queue user" ); CYG_ASSERT( stacksize >= PTHREAD_STACK_MIN, "Inadequate stack size supplied"); CYG_ASSERT( ticks != 0, "Zero tick count"); To sum it up: - Some eCos developers use assertion messages to say what failed - Some eCos developers use assertion messages to say what would have passed This inconsistency confuses people like me, new to eCos and debugging something which I don't fully understand yet. Any further comments/opinions? - Daniel -- View this message in context: http://sourceware-org.1504.n7.nabble.com/Typo-in-assert-error-message-causing-confusion-tp245807p245957.html Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss