From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15193 invoked by alias); 22 Jul 2002 19:27:44 -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 15186 invoked from network); 22 Jul 2002 19:27:44 -0000 Received: from unknown (HELO sccrmhc02.attbi.com) (204.127.202.62) by sources.redhat.com with SMTP; 22 Jul 2002 19:27:44 -0000 Received: from C1830598A ([12.234.169.231]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020722192743.VAWK6023.sccrmhc02.attbi.com@C1830598A> for ; Mon, 22 Jul 2002 19:27:43 +0000 Message-ID: <003a01c231b6$742bed80$0a00a8c0@C1830598A> From: "NavEcos" To: Date: Mon, 22 Jul 2002 12:27:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Subject: [ECOS] profiler & memory leak detector X-SW-Source: 2002-07/txt/msg00344.txt.bz2 Try as I may, I cannot post this to the ecos-devel list, although I am signed up for it, so I'm going to post it here in the discussion list. Has or does anybody use vxWorks? If you have, you may have used their profiler. I have a very simple profiler that I can make available for the x86 PC target. I would like to know if there would be any interest in making such a beast available in the main tree? It requires a modification in the kernel in vectors.S. Basically, I just detect interrupts with vector 0x20 (the 10 msec interrupt) and record the last function the program was in when the periodic system tick fired. I know this has some problems, namely anything that has a delay is tied to the system tick, but for stressed systems it gives a pretty accurate view of what functions you have to streamline. VxWorks also has a tool called memtool. It just detects which functions (and if memory serves tasks) allocate and dealloc memory and in which heap. This is useful for detecting memory leaks although not extremely useful. I don't have a similar tool, but I can make one. Is there any interest in putting these into the main tree? Putting in HOOKS to do it is very easy, and I would like to do that if there is any interest in incorporating it into the main tree. The profiler is very architecture dependant so I need help making that work for other platforms than x86 PC. -Rich -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss