From: Linux Mercedes <linuxmercedes@gmail.com>
To: duane@duaneellis.com
Cc: gdb@sourceware.org
Subject: Re: gdb cannot find "../sysdeps/unix/syscall-template.S"
Date: Thu, 14 Jan 2016 22:22:00 -0000 [thread overview]
Message-ID: <CANq-9Dg8Uf9hUKg1LQL1_Hn1-s1jeTHnMgBhFwLY41FgAzv2oQ@mail.gmail.com> (raw)
In-Reply-To: <20160114144731.5c1bb9f86d671edec44bb378f25c04cc.7a526e7354.wbe@email03.secureserver.net>
> Why does this happen?
Neat! That makes sense; thanks for explaining the details.
> What is the true fix? The distribution you are using (ie: I'm using
> Ubuntu) should *NOT* compile these files for GLIBC with debug records
> turned on (or the should *STRIP* all debug info from the object files
> and/or library).
> Also note: Debug records might not be *IN* the object, they could be in
> a parallel file (next to, or similar place) and the debugger knows how
> to find the corresponding symbol files for each library.
Aha! Turns out I somehow had the libc6-dbg package installed. Removing
it fixes the 'No such file or directory' issue.
It still prints 'Continuing.', but I'll have to sit down with the DDD
manual and see what it's doing to fix that.
Thanks!
next prev parent reply other threads:[~2016-01-14 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 21:07 Linux Mercedes
2016-01-14 21:10 ` Jan Kratochvil
2016-01-14 22:11 ` Linux Mercedes
2016-01-14 22:23 ` Jan Kratochvil
2016-01-15 0:02 ` Mike Frysinger
2016-01-15 8:05 ` Jan Kratochvil
2016-01-14 22:25 ` Jan Kratochvil
2016-01-14 21:55 ` Mike Frysinger
2016-01-14 21:47 ` duane
2016-01-14 22:22 ` Linux Mercedes [this message]
2016-01-15 9:34 ` Andreas Schwab
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=CANq-9Dg8Uf9hUKg1LQL1_Hn1-s1jeTHnMgBhFwLY41FgAzv2oQ@mail.gmail.com \
--to=linuxmercedes@gmail.com \
--cc=duane@duaneellis.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