From: "Fred J." <phddas@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: compiler problem
Date: Sun, 24 Jul 2005 19:48:00 -0000 [thread overview]
Message-ID: <20050724194826.14555.qmail@web53913.mail.yahoo.com> (raw)
Hello
I asked this question in other mailing lists, emacs,
gnu gdb, gnu make, and it may well be a compiler
problem.
my compiler is gcc 3.3.5-3, the debian testing
package.
I read that "Executable programs sometimes do not
record the directories of the source files from which
they were compiled, just the names.
I have this arrangement
sam@debian:~/Exercies/ThinkingInC++/Vol1/C03$ tree
.
|-- makefile
|-- 13
| |-- #rotation.cpp#
| |-- bitwise.cpp
| |-- makefile
| |-- printBinary.cpp
| |-- printBinary.h
| |-- proj1
| |-- rotation.cpp
| `-- semantic.cache
|-- 14
| |-- #makefile#
| |-- main.cpp
| |-- makefile
| |-- proj1
| |-- semantic.cache
| `-- semantic.cache~
../14/makefile looks like this
**************************************************
include ../makefile
in the parent directory I have this makefile
**************************************************
OBJS = main.o
CFLAGS= -g -Wall
proj1 : $(OBJS)
$(CXX) $(CFLAGS) -o $@ $(OBJS) #CC -o proj1 $(OBJS)
the macro @ evaluates to the current target.
clean :
rm -f $(OBJS)
I did
sam@debian:~/Exercies/ThinkingInC++/Vol1/C03/13$ make
which went ok.
how can I know if the executable programs did or did
not record the directories of the source files from
which it was compiled. and if it did what are they?
the reason I am asking is because when I
Run gdb (like this): gdb
~/Exercies/ThinkingInC++/Vol1/C03/13/proj1
I get
Current directory is
/home/sam/Exercies/ThinkingInC++/Vol1/C03/13/
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General
Public License, and you are welcome to change it
and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as "i386-linux"...Using host
libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) break bitwise.cpp : 11
No source file named bitwise.cpp. <-----this problem
Make breakpoint pending on future shared library load?
(y or [n])
(gdb) show directories
Source directories searched: $cdir:$cwd
(gdb)
and while we are at it, how to fix this, because
(gdb) dir /home/sam/Exercies/ThinkingInC++/Vol1/C03/13
Source directories searched:
/home/sam/Exercies/ThinkingInC++/Vol1/C03/13:$cdir:$cwd
(gdb) show directories
Source directories searched:
/home/sam/Exercies/ThinkingInC++/Vol1/C03/13:$cdir:$cwd
(gdb) break bitwise.cpp : 11
No source file named bitwise.cpp.
Make breakpoint pending on future shared library load?
(y or [n])
thanks
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
next reply other threads:[~2005-07-24 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 19:48 Fred J. [this message]
2005-07-24 20:50 ` Alex J. Dam
2005-07-25 16:09 ` Travis Spencer
2005-07-25 20:28 ` Fred J.
2005-07-26 6:08 ` Travis Spencer
-- strict thread matches above, loose matches on Subject: below --
1999-12-02 5:42 Nicole Bogeajis
1999-12-02 13:44 ` Arthur Gold
1999-12-31 22:24 ` Arthur Gold
1999-12-31 22:24 ` Nicole Bogeajis
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=20050724194826.14555.qmail@web53913.mail.yahoo.com \
--to=phddas@yahoo.com \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).