From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Nirf <quicknir@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Help with Code in Multiple Directories
Date: Fri, 27 Mar 2009 15:33:00 -0000 [thread overview]
Message-ID: <8ac60eac0903270833u7b38c03o2aee62a8c5365090@mail.gmail.com> (raw)
In-Reply-To: <22737823.post@talk.nabble.com>
On Fri, Mar 27, 2009 at 1:43 AM, Nirf <quicknir@gmail.com> wrote:
> I'm trying to get started with GDB but am having great trouble.
On what platform? Using which version of GDB?
Note that on Linux, or any other platform that uses DWARF
debug format, you shouldn't need to specify 'directory ...'
at all if you build and debug on the same machine: compiler
already supplies all the info GDB needs to find sources
regardless of where in file system they are located.
> However when I type in a command like "list sourcecodename:5" it does not
> find the source code regardless of which file name I insert for
> sourcecodename.
Did you build your program with debugging info (the '-g' GCC option) ?
Cheers,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-03-27 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 8:44 Nirf
2009-03-27 15:33 ` Paul Pluzhnikov [this message]
2009-03-27 21:40 ` Paul Pluzhnikov
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=8ac60eac0903270833u7b38c03o2aee62a8c5365090@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=quicknir@gmail.com \
/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