From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21311 invoked by alias); 8 Sep 2011 12:57:00 -0000 Received: (qmail 21299 invoked by uid 22791); 8 Sep 2011 12:56:59 -0000 X-SWARE-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 08 Sep 2011 12:56:25 +0000 Received: from isper.nabble.com ([192.168.236.156]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1R1e9Y-0003xz-Fx for gdb-patches@sourceware.org; Thu, 08 Sep 2011 05:56:24 -0700 Message-ID: <32423483.post@talk.nabble.com> Date: Thu, 08 Sep 2011 13:09:00 -0000 From: logitech To: gdb-patches@sourceware.org Subject: Re: Integration of timed breakpoints into GDB In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <32418104.post@talk.nabble.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-09/txt/msg00131.txt.bz2 Hi, This breakpoint functions as any normal breakpoint in gdb with the only added advantage that it can be invoked at a particular time. If in a blocking syscall, the program execution would be interrupted at the specified time as it would receive a SIGINT signal. Basically it would function the same as having a normal break statement in gdb. The use of this feature is in Real time systems which have a strict time constraint and if we want to know how much the program has executed in a specified time. It can also help in sampling data at a particular frequency. Cheers. Abhijit Halder wrote: > > On Wed, Sep 7, 2011 at 11:12 PM, logitech wrote: >> >> Hello, >> I have attached a patch file which integrates timed breakpoints into gdb. >> http://old.nabble.com/file/p32418104/patchfile.patch patchfile.patch >> The format of the command is "break 'x's 'y'us" where 's' and 'us' stand >> for >> seconds and microseconds respectively. Eg. break 1s 0us >> When the program execution begins, it breaks after 1sec. On continuing, >> the >> program resumes again and breaks after 1 sec. >> To continuously break the program after a specific time interval a >> separate >> script can be written as shown : >> >> break 0s 500us >> run >> while(1) >> p $pc >> c >> end >> quit >> >> Further details about the implementation can be found here >> http://www.youtube.com/watch?v=PAFQlxqI7qs&feature=player_embedded#! GDB >> Timed breakpoint >> >> I would highly appreciate comments and feedback from your side regarding >> the >> same. >> Thank you. >> >> -- >> View this message in context: >> http://old.nabble.com/Integration-of-timed-breakpoints-into-GDB-tp32418104p32418104.html >> Sent from the Sourceware - gdb-patches mailing list archive at >> Nabble.com. >> >> > > I have not yet seen the patch, but before that I would like to get > answer of few questions: > 1. What happen if your program execution is stuck inside a > blocking syscall when it should break? I believe the time you are > talking about is not a hard bound limit. > > 2. What is the usecase of this feature? > > -Abhijit > > -- View this message in context: http://old.nabble.com/Integration-of-timed-breakpoints-into-GDB-tp32418104p32423483.html Sent from the Sourceware - gdb-patches mailing list archive at Nabble.com.