- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I started to use intel inspector xe 2011 on linux suse.
After compiling the project with gcc, I start the analyze with the inspector, it does find errors but don't show me the errors in the source code? I tried setting the path, but didn't help.
What could it be?
This message appears in the source window: "Source File not Found. Assembly code is shown instead of source file. Source:"
Any ideas?
Thanks in advance
Emanuel
Link Copied
6 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As I said in other thread, add "-g" option to build. -peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Peter,
thanks for your answer! An indeed it worked for the simple code.
But for the project I wanted to use intel inspector, it does not work. The project is written in c and the code is separated in a large set of sub functions? Can this cause the problem?
I compile the program with a make filein following format:
************Makefile
PROG =name
SRCS = file1.c file2.c
OBJS = file1.o file2.o
LIBS = -lm /usr/local/lib/libfftw.a /usr/local/lib/librfftw.a
CC = gcc -fopenmp
CFLAGS = -O0 -g -ILibs
FC = f77
FFLAGS = -O
F90 = f90
F90FLAGS = -O
LDFLAGS = -s
all: $(PROG)
$(PROG): $(OBJS)
$(CC) $(LDFLAGS) -o $@ $(OBJS) $(LIBS)
clean:
rm -f $(PROG) $(OBJS) *.mod
.SUFFIXES: $(SUFFIXES) .f90
.f90.o:
$(F90) $(F90FLAGS) -c $
file1.o: file1_incld.h
************EOF
What could it be?
Yours,
Emanuel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Emanuel,
For CFLAGS, that is OK!
For F90FLAGS,I suggest touse "F90FLAGS=-O0 -g -debug inline-debug-info"
Thanks, Peter
For CFLAGS, that is OK!
For F90FLAGS,I suggest touse "F90FLAGS=-O0 -g -debug inline-debug-info"
Thanks, Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Peter,
I tried what you supposed but it didn't worked. Now I try to use icc compiler,
here i would use following flags:
CC = icc -openmp
CFLAGS = -O0 -g -ILibs
I think maybe the code structure is too complex, as the parallel for loop is in a subsub function?
Thanks anyway, I will come back if I have further questions or some solution.
Yours, Emanuel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not sure what "the code is separated in a large set of sub functions" means, but if your source is spread out over several or more directories, you need to use the Search Directories tab of the Project Properties dialog to tell the tool where to find the source files.
![](/skins/images/8492E06DAD1A420837AF16E991F628F9/2021_redesign/images/image_not_found.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello MrAnderson
with "the code is separated in a large set of sub functions" I wanted to say that the multi tread loop in a sub function: I try to explain it with a diagram
main
- function 1 in main
- function 2 in function 1
- function 3 in function 2
paralleled loop
I hope it is more clear now. The individual functions are all in separated files.
My source files are all in the same directory, where I set the path to.
What else could it be?
Yours,
Emanuel
![](/skins/images/B7BA37F9CE4B52FF7CAE1FB0388839C8/responsive_peak/images/icon_anonymous_message.png)
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page