From: Igor Korot <ikorot@earthlink.net>
To: gdb@sourceware.org
Subject: What do I need to look at the source while debugging?
Date: Wed, 11 Jun 2008 16:26:00 -0000 [thread overview]
Message-ID: <4779653.1213201568391.JavaMail.root@elwamui-little.atl.sa.earthlink.net> (raw)
Hi, ALL,
First a question: Is there anybody that using Gentoo + Portage?
And now to the problem:
I have a Gentoo box installed. On it I have a GNOME with KDevelop,
wxGTK, unixODBC and gdb. GNOME, KDevelop and gdb installed through
Portage. wxGTK is hand compiled and installed.
I installed unixODBC-2.2.12 using following:
'PORTAGE_TMPDIR=/home/igor FEATURES="noclean keepwork" emerge unixODBC'
Then I change permissions on the /home/igor/portage/dev-db directory
to make it accessible to my user 'igor'.
Next, I started KDevelop, open the file /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/Drivers/SQLConfigDataSource.c (it did open fine).
I put a breakopint in that function, and started my program.
At this point I received following message:
no file named /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/Drivers/SQLConfigDataSource.c.
No my questions are:
1. What else is required in order to follow through the source code?
2. Do I have to run the program from the unixODBC source directory?
3. Maybe I just need to change a permissions/ownership of the source tree
of unixODBC files?
Thank you.
next reply other threads:[~2008-06-11 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 16:26 Igor Korot [this message]
2008-06-11 17:16 ` Michael Snyder
2008-06-11 17:54 Igor Korot
2008-06-11 18:44 ` Michael Snyder
2008-06-12 4:34 Igor Korot
2008-06-15 4:02 Igor Korot
2008-06-15 20:06 ` Michael Snyder
2008-06-15 21:53 Igor Korot
2008-06-15 22:27 ` Michael Snyder
2008-06-16 1:09 Fahd Abidi
2008-06-16 4:50 Igor Korot
2008-06-16 16:06 Igor Korot
2008-06-16 16:41 ` Daniel Jacobowitz
2008-06-16 17:17 Igor Korot
2008-06-16 17:38 ` Michael Snyder
2008-06-16 18:42 Igor Korot
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=4779653.1213201568391.JavaMail.root@elwamui-little.atl.sa.earthlink.net \
--to=ikorot@earthlink.net \
--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