Delete a watchpoint by address to automate segfault tracking

["Laurent G." <vrygoud@gmail.com>]

Hi,

I'm debugging a segfault in a pretty large real-time program (the kind
of which we can't figure out what's wrong just by looking at the
code).

In short, I know where the program crash (non-valid pointer) but I
don't known who and when my pointer gets corrupted, as the program
alloc & destroy 2/3 similar buffers by second.

I find out a nice technique is this article
(http://www.outflux.net/blog/archives/2007/09/15/catching-stack-overflows-in-gdb-as-they-happen/)
which automate the creation of watchpoint on malloced buffer:
(gdb) commands 1
>silent
>set variable $m = p_mypointer
>watch *$m
>cont
>end

In the article, the author says "I couldn’t find an easy way to track
the memory watch number that was created during the first breakpoint,
I just built a gdb counter, and deleted the memory watch when leaving,
since I could predict gdb’s numbering" and implements watchpoints
destruction this way:
(gdb) set variable $count = 3
(gdb) commands 2
>silent
>delete $count
>set variable $count = $count + 1
>cont
>end

This technique works well when the buffers get destroyed in the same
order than there are created. But in my program this is not the case.

From the value passed to free() I can get the memory address of the
to-be-destroyed buffer, but I couldn't find a way to tell GDB to
delete that specific watchpoint:

(gdb) delete *0x080483c6
-> OK but can't be automated

(gdb) set variable $d = p_mypointer
(gdb) p $d
0x080483c6
(gdb) d $d
-> Can't do. "Convenience variables used in line specs must have
integer values."

How can I do a "delete *`print $d`" in GDB?
Thanks!

Regards,
Laurent