From: vijay nag <vijunag@gmail.com>
To: gdb@sourceware.org
Subject: RE: amd64 executable debugging
Date: Sat, 24 Mar 2018 13:14:00 -0000 [thread overview]
Message-ID: <CAKhyrx8vBjMg+140b8XWLnw92-J1oh206sO6UOtR7X7BCnDL+w@mail.gmail.com> (raw)
In-Reply-To: <CAKhyrx9t6VGEe5Zc-KwO3Cp-KLV+JUqtCnbQaUK7qcQqToz2aA@mail.gmail.com>
Hello GDB,
Most often while debugging amd64 executable, GDB throws '<variable
optimized out>' error and also sometimes when function parameters are
passed on register GDB reports incorrect information in few frames. I'm
sure in 64 bit with more registers available, there is more revenue for
optimization, it is entirely possible that GDB gets confused due to that
and information provided by GDB isn't reliable sometimes. I'm wondering if
the latest GDB has somehow solved this problem Or disassembling and
studying instructions is the only way to go about it ? Also, is there a way
to increase this debug-ability by adding any additional compiler flags ?
--Vijay--
next parent reply other threads:[~2018-03-24 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKhyrx-QBqN85fXQnoE+4c9B84xsUZ+DroFfjHQPcXxX5d9kjg@mail.gmail.com>
[not found] ` <CAKhyrx-DKjK0rBxnZF8AfmxyX92esSqhkV5g8xL6TDOXMn4qcQ@mail.gmail.com>
[not found] ` <CAKhyrx9tfUc5qkWfeTAURJovHvjQN0g2zER-iKiuP+gyvx9Z+g@mail.gmail.com>
[not found] ` <CAKhyrx-pEi+jJD9zAvUpcuMeY3nocB1VVKv6ro8DE6m-8NYGuA@mail.gmail.com>
[not found] ` <CAKhyrx9C9R7_AJaL8YC2Wz74Hk+-FtxMcOoZQPPztmDnSOyVGw@mail.gmail.com>
[not found] ` <CAKhyrx-7=dJOB9Mz=JdauejT7QLyJA4iAjNiH+fejsX397=bHA@mail.gmail.com>
[not found] ` <CAKhyrx8XLzP1MKp_YZFE0nmk1Q51WRXNMEzO5kHNjjB5ypWk5g@mail.gmail.com>
[not found] ` <CAKhyrx-Pc5KZbtyPSOAc+XLJNDXYsJG9umZCFShLrJ54ELMtiA@mail.gmail.com>
[not found] ` <CAKhyrx84JMZ2tBB2FE0gux8aF2Jd9k8571ni6-u4w3G5Chy8Dw@mail.gmail.com>
[not found] ` <CAKhyrx-3h2KAU4jy2t_fbYZa32ZwZRYdZuB==oBvKtQQzq1v3w@mail.gmail.com>
[not found] ` <CAKhyrx_cATMnN_R6BL+X0mynNw7rLh2b7ekmbrEZsG3AV8wP_A@mail.gmail.com>
[not found] ` <CAKhyrx8B3AD6BR8Obi-2mALfrbk20bE3J6EJa=87-Qr4XBwwMQ@mail.gmail.com>
[not found] ` <CAKhyrx-q-+LBActXatdDqFZCUCTdMFxqEYvz9pMTRBK4ahX8uQ@mail.gmail.com>
[not found] ` <CAKhyrx9LHywr=zK7w5k+VL=WQF+xuMK+=Y4sL+F_BOAq0rjKMQ@mail.gmail.com>
[not found] ` <CAKhyrx88oQECMaR8jYtgSgr4V4HQ_7vdiSYmg-OD3m8+RhvtQQ@mail.gmail.com>
[not found] ` <CAKhyrx9Y7GSN0PrUBYsPi63ngQKkpsyNbMf5+x6TBpinqF=D2Q@mail.gmail.com>
[not found] ` <CAKhyrx8tH6bCziypL_aDiyF_x0HZt6TQQa1gSSdW-eYEB1AEEA@mail.gmail.com>
[not found] ` <CAKhyrx9jKJShS2rgL9S=h3rpqq++mB6j=8Y88UXJ9dn7DbwB+g@mail.gmail.com>
[not found] ` <CAKhyrx9t6VGEe5Zc-KwO3Cp-KLV+JUqtCnbQaUK7qcQqToz2aA@mail.gmail.com>
2018-03-24 13:14 ` vijay nag [this message]
2018-03-24 17:03 ` Simon Marchi
2018-03-25 6:02 ` vijay nag
2018-03-25 6:04 ` vijay nag
2018-03-25 11:35 ` Simon Marchi
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=CAKhyrx8vBjMg+140b8XWLnw92-J1oh206sO6UOtR7X7BCnDL+w@mail.gmail.com \
--to=vijunag@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