PGI User Forum
 SearchSearch   MemberlistMemberlist     RegisterRegister   ProfileProfile    Log inLog in 

Free OpenACC Webinar

WARNING: invalid symbol information detected for pointer typ

 
Post new topic   Reply to topic    PGI User Forum Forum Index -> Debugging and Profiling
View previous topic :: View next topic  
Author Message
George_B



Joined: 09 Sep 2008
Posts: 2

PostPosted: Tue Sep 09, 2008 8:43 am    Post subject: WARNING: invalid symbol information detected for pointer typ Reply with quote

Hi all,

Relative newbie here, but I get an interesting warning when trying to debug my code with pgdbg.

There are many files in the program, but when I switch to the file I am interested in debugging within pgdbg, it says:

WARNING: invalid symbol information detected for pointer type

multiple times. From there, all the line numbers are greyed out, and I get errors when trying to set breakpoints

ERROR: Cannot set breakpoint at line:...

The other files in the code seem to want to debug ok, and the code itself runs perfectly well, even with all the debugging flags. The file in question contains a module, though even the routines/functions outside this module cannot have breakpoints set. I think the problem may be to do with the following construct in the module which it is having difficulty with:

Code:

TYPE ExcitGenerator
        INTEGER , ALLOCATABLE :: ExcitData(:)
        INTEGER :: nExcitMemLen               
        LOGICAL :: ExitGenForDet=.false.
END TYPE
TYPE(ExcitGenerator) , ALLOCATABLE , TARGET :: WalkVecExcits(:),WalkVec2Excits(:)
TYPE(ExcitGenerator) , POINTER :: CurrentExcits(:), NewExcits(:)


In the program, I allocate WalkVec(2)Excits, which are pointed to by CurrentExcits/NewExcits. I then allocate/deallocate the individual ExcitData components as I need them. This works fine when running the code, and may not be the cause of pgdbg's problem.

I compile the file with pgf90 -c -g -r8 pc=64 -Msignextend -Minform=warn -Msecond_underscore -Mfree FciMC.f90

Hope you can help.
Thanks
Back to top
View user's profile
George_B



Joined: 09 Sep 2008
Posts: 2

PostPosted: Tue Sep 09, 2008 8:45 am    Post subject: Reply with quote

I thought i'd mention that I'm using PGDBG 7.2-2 x86-64 if thats an issue.

Thanks again
Back to top
View user's profile
mkcolg



Joined: 30 Jun 2004
Posts: 6218
Location: The Portland Group Inc.

PostPosted: Thu Sep 11, 2008 10:21 am    Post subject: Reply with quote

Hi George,

I sent this on to our tools engineers who believe it might be an issue with the use of "-Msecond_underscore" and the debugger not resolving how the symbol is decorated. Can you please send an example to PGI customer support at trs@pgroup.com so we can have out engineers take look?

Also, do need "-Msecond_underscore" for GNU compatibility or are you able to compile your code without the flag?

Thanks,
Mat
Back to top
View user's profile
mkcolg



Joined: 30 Jun 2004
Posts: 6218
Location: The Portland Group Inc.

PostPosted: Fri Oct 17, 2008 1:24 pm    Post subject: Reply with quote

Hi George,

Our tools team has tried multiple configurations but has been unable to reproduce the problem. Can you please send and example to PGI customer support at trs@pgroup.com?

Thanks,
Mat
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    PGI User Forum Forum Index -> Debugging and Profiling All times are GMT - 7 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © phpBB Group