From: Julien Chavanton <jchavanton@gmail.com>
To: Doug Evans <xdje42@gmail.com>, gdb@sourceware.org
Subject: Re: how to create and hardware watchpoint from a commands list.
Date: Sun, 08 Feb 2015 14:49:00 -0000 [thread overview]
Message-ID: <CAKmcL2kkSkTGrTdWWfz2ExtJygahYw7DML5JuT66RpuWXvtW_w@mail.gmail.com> (raw)
In-Reply-To: <CAP9bCMQknJ15bb52HPPq8ESa+=JOdhAxK=fTd45hxKVsep0qkQ@mail.gmail.com>
Hi Doug, thank you for trying to help, I spent a few hours on this so
I am interested to solve this puzzle for next time.
----------------------------
By doing it manually I mean,
step-1) I type :
printf "0x%x\n", &call->stream->session->ext.settings.mode
and then :
step-2) I type :
watch *(int *){result from step 1}
-------------------------------
This did not work for me :
watch -location call->stream->session->ext.settings.mode
-------------------------------
I can rerun the session and provide exact output or I could just try
an alternative "piping" the output of step-1 to step-2 from the GDB
"command line interpreter" not sure how it is called, this as to be
executed from a breakpoint command list ?
On Sun, Feb 8, 2015 at 5:26 AM, Doug Evans <xdje42@gmail.com> wrote:
> On Wed, Feb 4, 2015 at 2:14 AM, Julien Chavanton <jchavanton@gmail.com> wrote:
>> Hi Folks, I would like to create and hardware watchpoint from a commands list.
>>
>> retrieve the addres of a variable and create a watch.
>>
>> watch *(int *) &call->stream->session->ext.settings.mode
>>
>> Manualy this is working fine, but I do not know the right syntax in GDB.
>
> What do you mean by this working manually but then not knowing the right syntax?
>
>>
>> I tried "watch -location call->stream->session->ext.settings.mode"
>>
>> And sereval other things, is there a way to pipe the output of one
>> command to another one ?
>
> You tried several things, but you need to be more specific about
> what problems you had. Complete unedited session logs are useful.
>
> There are various ways to "pipe" (for lack of a better term) the
> output of previous commands into subsequent commands.
> value history, convenience variables and/or eval or python come to mind.
> But do you need to?
> What about "watch -location ..." didn't work?
>
>>
>> watch *(int *) | printf "0x%x\n", &call->stream->session->ext.settings.mode
>>
>>
>> ----------------------------------------------------------
>>
>>
>> define myhook
>> echo myhook \n
>> next
>> next
>> next
>> print call->stream->session->ext.settings.mode
>> print &call->stream->session->ext.settings.mode
>> printf "watch *(int *)0x%x\n", &call->stream->session->ext.settings.mode
>> end
>>
>> break set_settings
>> commands
>> myhook
>> end
next prev parent reply other threads:[~2015-02-08 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 10:14 Julien Chavanton
2015-02-08 5:26 ` Doug Evans
2015-02-08 14:49 ` Julien Chavanton [this message]
2015-02-08 21:47 ` Doug Evans
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=CAKmcL2kkSkTGrTdWWfz2ExtJygahYw7DML5JuT66RpuWXvtW_w@mail.gmail.com \
--to=jchavanton@gmail.com \
--cc=gdb@sourceware.org \
--cc=xdje42@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