From: Abhijit Halder <abhijit.k.halder@gmail.com>
To: logitech <supriya.rao17@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Integration of timed breakpoints into GDB
Date: Thu, 08 Sep 2011 12:57:00 -0000 [thread overview]
Message-ID: <CAOhZP9yEN6Q9bTygAUgAMuuNVzUBq2Sd=iMqg4wGNj+6N0wsPQ@mail.gmail.com> (raw)
In-Reply-To: <32418104.post@talk.nabble.com>
On Wed, Sep 7, 2011 at 11:12 PM, logitech <supriya.rao17@gmail.com> 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
next prev parent reply other threads:[~2011-09-08 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 23:11 logitech
2011-09-08 1:30 ` Keith Seitz
2011-09-08 12:57 ` Abhijit Halder [this message]
2011-09-08 13:09 ` logitech
2011-09-10 12:46 ` Jan Kratochvil
2011-10-03 17:46 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOhZP9yEN6Q9bTygAUgAMuuNVzUBq2Sd=iMqg4wGNj+6N0wsPQ@mail.gmail.com' \
--to=abhijit.k.halder@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=supriya.rao17@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox