From: Nagmat Nazarov <nagmat@gmail.com>
To: Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Need real life synthetic use cases for debugging
Date: Thu, 7 Jan 2021 16:40:54 +0900 [thread overview]
Message-ID: <CAJnvuZ80vuCArk1AXOde1JBz2iQ538X5Jb=72w4sLykbx90T+A@mail.gmail.com> (raw)
We have *implemented PrC(program context) register* which adds program
counter value of instruction where we have* jump (JAL or JALR) instruction* on
RISC-V architecture. By using *PrC* we can* set breakpoints on exact order
of function calls*. We example below you can see PrC values of function
call graph where f1,f2 and f3 are functions:
PATH
PrC
f1
9c6
f1->f2
1246
f1->f2->f3
19be
f1->f3
12ac
f1->f3->f2
18c0
f2
a04
f2->f1
111c
f2->f1->f3
1a02
f2->f3
117c
f2->f3->f1
1742
f3
a42
f3->f1
1008
f3->f1->f2
1888
f3->f2
1056
f3->f2->f1
176e
As you see all PrC values are different from each other. By using PrC I can
set breakpoints on consecutive chain of function calls. Now I need real
life synthetic cases where I can use this method. Any help is appreciated.
Kind regards,
Nagmat
nagmat@gmail.com
reply other threads:[~2021-01-07 7:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJnvuZ80vuCArk1AXOde1JBz2iQ538X5Jb=72w4sLykbx90T+A@mail.gmail.com' \
--to=nagmat@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).