This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
RE: amd64 executable debugging
- From: vijay nag <vijunag at gmail dot com>
- To: gdb at sourceware dot org
- Date: Sat, 24 Mar 2018 18:44:30 +0530
- Subject: RE: amd64 executable debugging
- References: <CAKhyrx-QBqN85fXQnoE+4c9B84xsUZ+DroFfjHQPcXxX5d9kjg@mail.gmail.com> <CAKhyrx-DKjK0rBxnZF8AfmxyX92esSqhkV5g8xL6TDOXMn4qcQ@mail.gmail.com> <CAKhyrx9tfUc5qkWfeTAURJovHvjQN0g2zER-iKiuP+gyvx9Z+g@mail.gmail.com> <CAKhyrx-pEi+jJD9zAvUpcuMeY3nocB1VVKv6ro8DE6m-8NYGuA@mail.gmail.com> <CAKhyrx9C9R7_AJaL8YC2Wz74Hk+-FtxMcOoZQPPztmDnSOyVGw@mail.gmail.com> <CAKhyrx-7=dJOB9Mz=JdauejT7QLyJA4iAjNiH+fejsX397=bHA@mail.gmail.com> <CAKhyrx8XLzP1MKp_YZFE0nmk1Q51WRXNMEzO5kHNjjB5ypWk5g@mail.gmail.com> <CAKhyrx-Pc5KZbtyPSOAc+XLJNDXYsJG9umZCFShLrJ54ELMtiA@mail.gmail.com> <CAKhyrx84JMZ2tBB2FE0gux8aF2Jd9k8571ni6-u4w3G5Chy8Dw@mail.gmail.com> <CAKhyrx-3h2KAU4jy2t_fbYZa32ZwZRYdZuB==oBvKtQQzq1v3w@mail.gmail.com> <CAKhyrx_cATMnN_R6BL+X0mynNw7rLh2b7ekmbrEZsG3AV8wP_A@mail.gmail.com> <CAKhyrx8B3AD6BR8Obi-2mALfrbk20bE3J6EJa=87-Qr4XBwwMQ@mail.gmail.com> <CAKhyrx-q-+LBActXatdDqFZCUCTdMFxqEYvz9pMTRBK4ahX8uQ@mail.gmail.com> <CAKhyrx9LHywr=zK7w5k+VL=WQF+xuMK+=Y4sL+F_BOAq0rjKMQ@mail.gmail.com> <CAKhyrx88oQECMaR8jYtgSgr4V4HQ_7vdiSYmg-OD3m8+RhvtQQ@mail.gmail.com> <CAKhyrx9Y7GSN0PrUBYsPi63ngQKkpsyNbMf5+x6TBpinqF=D2Q@mail.gmail.com> <CAKhyrx8tH6bCziypL_aDiyF_x0HZt6TQQa1gSSdW-eYEB1AEEA@mail.gmail.com> <CAKhyrx9jKJShS2rgL9S=h3rpqq++mB6j=8Y88UXJ9dn7DbwB+g@mail.gmail.com> <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--