Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Lassi Niemistö" <lassi.niemisto@wapice.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Build root location affects debugging on PowerPC
Date: Wed, 30 Aug 2017 12:18:00 -0000	[thread overview]
Message-ID: <b47df57722f04244a042201420d2abff@EDB3.wapice.localdomain> (raw)
In-Reply-To: <659baa98c7344fd2af55c359c1133681@EDB3.wapice.localdomain>

Answering to myself:

Root cause for debugging to fail on PowerPC were the rpaths auto-planted into my binaries by CMake. After using set(CMAKE_SKIP_BUILD_RPATH TRUE), the debugging started working as it should independent from the build root location. Not sure why it was not an issue on my x86 build, maybe because there I add some rpaths manually and this may stop CMake from autoplanting them.
 
Tried my best to make the build completely deterministic but hitting the bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65015 and thus the CRC part of --add-gnu-debuglink  will still change my binary a little bit every time I build.
Another non-determinism is the LTO I use for some small binaries, but that is another discussion.

I am splitting the debug information to separate debug file using objcopy and thus have used --add-gnu-debuglink. If someone knows a way to allow the debugging without the link, I am interested.  

> will file a bug report about the 8.0 

It existed already, so just posted some material for easy recreation on any PC: https://sourceware.org/bugzilla/show_bug.cgi?id=21603

-Lassi N.


      reply	other threads:[~2017-08-30 12:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25  9:02 Lassi Niemistö
2017-08-30 12:18 ` Lassi Niemistö [this message]

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=b47df57722f04244a042201420d2abff@EDB3.wapice.localdomain \
    --to=lassi.niemisto@wapice.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