From: "Laurent G." <vrygoud@gmail.com>
To: gdb@sourceware.org
Subject: Re: Delete a watchpoint by address to automate segfault tracking
Date: Fri, 28 Sep 2012 13:32:00 -0000 [thread overview]
Message-ID: <CAD=JCDv+VSP3KXD4yYy+1w2N852pNMAeyeg9Q_6_0hbhO3VFVA@mail.gmail.com> (raw)
In-Reply-To: <87k3vfwpnv.fsf@fleche.redhat.com>
On Thu, Sep 27, 2012 at 3:39 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Laurent" == Laurent G <vrygoud@gmail.com> writes:
>
> Laurent> In the article, the author says "I couldn’t find an easy way to track
> Laurent> the memory watch number that was created during the first breakpoint,
> Laurent> I just built a gdb counter, and deleted the memory watch when leaving,
> Laurent> since I could predict gdb’s numbering" and implements watchpoints
> Laurent> destruction this way:
>
> I think $bpnum may hold this.
> See the 'Set Breaks' node of the manual.
> Or it can perhaps be done from Python.
>
> Laurent> How can I do a "delete *`print $d`" in GDB?
>
> A few ways.
>
> Simplest is to use "eval".
>
> Otherwise, Python.
>
> Otherwise, if you have an old gdb and can't upgrade, use set logging to
> write out a file with the command you want (using printf), then 'source'
> the file.
>
> Tom
Thanks for your reply that helped me a lot. In fact the true issue is that you
can clear a breakpoint by its address:
(gdb) clear *0x80a5f90
But for no reason (from a user point of view) you can't do the same thing for
a watchpoint. If it was possible I could have used:
(gdb) eval "delete *0x%x", my_pointer
Even if the Python support is great I forgot to tell that the target
is an embedded
system so I didn't want to compile a Python environment. Anyway, that's maybe
not the cleanest way to do so but I did the write-out-a-file things to match the
address of the buffer with the number of the watchpoint associated with it.
I'm positing my script bellow in the case anyone encounter the same issue:
(gdb) set pagination off
(gdb) b open_filter.c:30
(gdb) b close_filter.c:100
(gdb) commands 1
(gdb) silent
(gdb) watch -l *(int*)*p_data
(gdb) set logging file watchpoints.gdb
(gdb) set logging on
(gdb) eval "echo %d 0x%x\n", $bpnum, p_data
(gdb) set logging off
(gdb) cont
(gdb) end
(gdb) commands 2
(gdb) silent
(gdb) set logging file match.gdb
(gdb) set logging overwrite on
(gdb) set logging on
(gdb) eval "echo 0x%x\n", p_data
(gdb) set logging off
(gdb) set logging overwrite off
(gdb) shell cat watchpoints.gdb | grep `cat match.gdb` | awk -F" "
'{print "delete "$1}' > delete_wp.gdb
(gdb) shell line=`cat match.gdb`; sed -i "/$line/d" watchpoints.gdb
(gdb) source delete_wp.gdb
(gdb) cont
(gdb) end
Regards,
Laurent
prev parent reply other threads:[~2012-09-28 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 11:43 Laurent G.
2012-09-27 13:39 ` Tom Tromey
2012-09-28 13:32 ` Laurent G. [this message]
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='CAD=JCDv+VSP3KXD4yYy+1w2N852pNMAeyeg9Q_6_0hbhO3VFVA@mail.gmail.com' \
--to=vrygoud@gmail.com \
--cc=gdb@sourceware.org \
/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