From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10341] New: gdb install of py files when using buildroot toolchain includes build path
Date: Mon, 25 Sep 2017 21:03:36 +0000 [thread overview]
Message-ID: <bug-10341-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10341
Bug ID: 10341
Summary: gdb install of py files when using buildroot toolchain
includes build path
Product: buildroot
Version: 2017.08
Hardware: All
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: matthew.weber at rockwellcollins.com
CC: buildroot at uclibc.org
Target Milestone: ---
We noticed the build always pulls the path in under
./host/share/gdb/auto-load/* when installing some gdb python files. Haven't
dug further at this point.
i.e
./host/share/gdb/auto-load/home/johndoe/build_folder/host/lib/*.py
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-09-25 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 21:03 bugzilla at busybox.net [this message]
2017-10-31 21:15 ` [Buildroot] [Bug 10341] gdb install of py files when using buildroot toolchain includes build path bugzilla at busybox.net
2018-06-06 14:21 ` bugzilla at busybox.net
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=bug-10341-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.