public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "Daniel.Lehne@amk-drives.bg" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/13989] gdb invalid search order for shared libraries by cross debuging Date: Wed, 18 Apr 2012 12:33:00 -0000 [thread overview] Message-ID: <bug-13989-4717-Kjx7OVvPA4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13989-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13989 --- Comment #2 from Daniel <Daniel.Lehne@amk-drives.bg> 2012-04-18 12:31:59 UTC --- I've got this information from http://sourceware.org/gdb/onlinedocs/gdb/Files.html. "... `solib-search-path' is used after `sysroot' fails to locate the library, OR if the path to the library is relative instead of absolute." I've got a cross-toolchain (must stay untouched) as sysroot, which is not serving all libraries (additional jpeg, ...). So i could give a hint to GDB to a special folder(solib-search-path) _after_ sysroot. That was my idea to use solib-search-path, but pity it isn't available. So this is not a bug, rather unprecise points in the online documentation of solib-search-path. Thanks for the advices. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-04-18 12:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-18 11:30 [Bug gdb/13989] New: " Daniel.Lehne@amk-drives.bg 2012-04-18 11:50 ` [Bug gdb/13989] " palves at redhat dot com 2012-04-18 12:33 ` Daniel.Lehne@amk-drives.bg [this message] 2012-04-18 12:58 ` Daniel.Lehne@amk-drives.bg 2012-05-10 14:31 ` palves at redhat dot com 2012-09-28 19:50 ` palves at redhat dot com 2012-09-28 20:20 ` cvs-commit at gcc dot gnu.org 2012-09-28 21:10 ` palves at redhat dot com
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-13989-4717-Kjx7OVvPA4@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).