From: Krishna Narayanan <krishnanarayanan132002@gmail.com>
To: gcc@gcc.gnu.org
Subject: Doubts about the cp-demangler non recursive project.
Date: Sat, 29 Jan 2022 23:54:33 +0530 [thread overview]
Message-ID: <CABhGnjuhbzFCs2de6gNaN1gmAy3w8g_YBo1f6Hceb8CAHFwY3g@mail.gmail.com> (raw)
Respected Sir/Madam,
This is Krishna Narayanan a beginner in the gcc community.I have been
reading through a while about the cp-demangler non recursive project,
getting familiar with the basic terminologies about demangler.I would like
to work on it.
Topics which I have covered till now include extern C,C++ filt and about
function abi ::_cxa_demangle.
For the non recursive part I am going through the memory management of
C,stacks and heaps related to function calls, etc.Some basic theory related
to stack overflow and tried using fsanitize (address sanitizer) in the
basic program.Didnt get much clarity about the output of sanitizer but had
a overview of it.I am also familiar with gdb to some certain extent.
What should be my next step,am I on the right track for understanding the
concepts?It would be great if I could get some help about the upcoming
topics I should refer and how should I implement in this project.
Hoping to hear from you soon.
Thanks and Regards,
Krishna Narayanan.
reply other threads:[~2022-01-29 18:24 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=CABhGnjuhbzFCs2de6gNaN1gmAy3w8g_YBo1f6Hceb8CAHFwY3g@mail.gmail.com \
--to=krishnanarayanan132002@gmail.com \
--cc=gcc@gcc.gnu.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).