PGDBG does not run (win x64)

Accelerated Computing HPC Compilers Legacy PGI Compilers
1

I have problems to run PGDBG. This is an example of what happens in my Win x64 system. The error is always the same, and does not depend on the specific fortran program.

A simple program test.f90 (located in the c:\test directory) is compiled with the -g option and runs properly.

When I run pgdbg, an error message is displayed in the PGDBG console

SetScreenBufferSize failed: 87
db_init: configure console failed

and the PGDBG GUI shows the message:

ERROR: CANNOT LOAD c:\test\test.exe.

See below for details.
Thank you very much for your help.

==================
PGI Workstation 6.1-5 (x64)

PGI Workstation 6.1-5 (x64)
PGI$ cd c:\test
PGI$ pgf90 -g test.f90
PGI$ dir
pg.dll test.dwf test.exe test.f90 test.pdb
PGI$ pgdbg -I c:/test c:/test/test.exe
PGI$

==================
PGDBC Console

SetScreenBufferSize failed: 87
db_init: configure console failed

================================
PGDBG - The Portland Group (Command Prompt)

PGDBG 6.1-5 x86-64 (Workstation, 4 CPU)
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2006, STMicroelectronics, Inc. All Rights Reserved.
***Reading DWARFv2 Information.
ERROR: CANNOT LOAD c:\test\test.exe.

pgdbg>

2

Hi bruna,

I wasn’t able to recreate the issue here and our tools engineers have not seen this error before. I am wondering why you have a local copy of “pg.dll” in the directory. Was there an issue that you were trying to work around? Could this “pg.dll” be from an earlier release? What happens if you remove this local copy?

  • Mat
3

Hi Mat,

If I remove pg.dll from the c:\test directory, when I start test.exe, I get the error message:

====================
test.exe - Unable To Locate Component

This application has failed to start because pg.dll was not found. Re-installing the application may fix this problem.

pd.dll is the last available version.

\

  • Bruna
4

Hi Bruna,

From the PGI bash prompt (pgi.bat), what is the output from the following commands? I’d like to see how your environment is setup.

which pgf90
which pgdbg
echo $PGI
echo $PATH
dir $PGI/win64/6.1-5/bin
cat $PGI/win64/6.1-5/pgi.bat

Thanks,
Mat

5

Hi Mat,
hereafter you will find th info you requested:

PGI$ which pgf90
/c/PROGRA~1/PGI/win64/6.1-5/bin/pgf90
PGI$ which pgdbg
/c/PROGRA~1/PGI/win64/6.1-5/bin/pgdbg
PGI$ echo $PGI
C:\PROGRA~1\PGI
PGI$ echo $PATH
.:/c/PROGRA~1/PGI/win64/6.1-5/cygwin/bin:/c/PROGRA~1/PGI/win64/6.1-5/bin:/c/Program Files/Microsoft
Platform SDK/bin/win64/x86/AMD64:/c/Program Files (x86)/Java/jre1.5.0_06/bin:/c/WINDOWS/system32:/c/
WINDOWS:/c/WINDOWS/System32/Wbem:/c/Program Files (x86)/Microsoft SQL Server/90/Tools/binn/:.
PGI$ dir $PGI/win64/6.1-5/bin
ar.exe lmgrd.exe pgcc.rc pgf77.exe pgf95.exe pgprof.bat
ar.rc lmtools.exe pgcnv.exe pgf77.rc pgf95.rc pgroupd.exe
as64.exe lmutil.exe pgconsole.exe pgf77rc pgftn.exe pgsize.exe
ccrc local.rc pgcpp.exe pgf90.dll pgftn_ex.exe pgsmart.exe
cpprc nativerc pgcpp.rc pgf90.exe pgftnrc pgstrp.exe
fnativerc nt64rc pgcpp1.exe pgf90.rc pgftnrtl.dll ranlib.exe
installs.exe ntrc pgcpp2.exe pgf901.exe pgipa.exe ranlib.rc
iparc pg.dll pgcpp2ex.exe pgf902.dll pgmp.dll x8664rc
jh.jar pgappend.exe pgdbg pgf902.exe pgmunch.exe x86rc
jpgdbg.jar pgc.dll pgdbg.bat pgf90_ex.exe pgnm.exe
jpgprof.jar pgc.exe pgdbg1.exe pgf90_rpm1.dll pgprelnk.exe
libacml_dll.dll pgc_ex.exe pgdecode.exe pgf90rc pgprepro.exe
libacml_mp_dll.dll pgcc.exe pgextract.exe pgf90rtl.dll pgprof
PGI$ dir $PGI/win64/6.1-5/pgi.bat
C:\PROGRA~1\PGI/win64/6.1-5/pgi.bat
PGI$ cat $PGI/win64/6.1-5/pgi.bat
@echo off
set PGI=C:\PROGRA~1\PGI
set PATH=C:\Program Files (x86)\Java\jre1.5.0_06\bin;%PATH%
set PATH=C:\Program Files\Microsoft Platform SDK\bin\win64\x86\AMD64;%PATH%
set PATH=%PGI%\win64\6.1-5\bin;%PATH%
set LM_LICENSE_FILE=%PGI%\license.dat
set FLEXLM_BATCH=1
title PGI Workstation 6.1-5 (x64)
set TMP=C:\temp
set PS1=PGI$
echo PGI Workstation 6.1-5 (x64)
set CYGROOT=%PGI%\win64\6.1-5\cygwin
set PATH=.;%CYGROOT%\bin;%PATH%
set MANPATH=%PGI%\win64\6.1-5\man\man1::
set MAKE_MODE=unix
set MAN_CONF=%CYGROOT%\usr\share\misc\man.conf
set GROFF_FONT_PATH=%CYGROOT%\usr\share\groff\1.18.1\font
set GROFF_TMAC_PATH=%CYGROOT%\usr\share\groff\1.18.1\tmac
set MAGIC=%CYGROOT%\usr\share\file\magic
set TERMCAP=%CYGROOT%\etc\termcap
set TERM=ansi
set VIM=%CYGROOT%\usr\share\vim
bash
PGI$

Thanks
b.

6

Hi B,

Well, you’ve got us stumped on this one. Your environment looks ok. While you have a newer version Java, we installed it here locally and everything worked fine.

Please repeat the following commands (below) and post your output exactly as it is on the screen. Also, please encapsulate the output inside a “code” tag so that it formats correctly.

Thanks,
Mat

Open a PGI Workstation (x64) window via

Start–>All Programs–>PGI Workstation 6.1-5–>PGI Workstation (x64)

In that window run the following commands:

PGI$ cd c:\test
PGI$ rm pg.dll
PGI$ rm test.exe test.pdb test.dwf

PGI$ ls
test.f90

PGI$ cat test.f90
print *, "hi"
end

PGI$ pgf90 -g test.f90

PGI$ test.exe
 hi

PGI$ pgdbg -text test.exe
PGDBG 6.1-5 x86-64 (Workstation, 4 CPU)
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2006, STMicroelectronics, Inc. All Rights Reserved.
***Reading DWARFv2 Information.
[0] New Thread (TID 2396)
Loaded: c:\test\test.exe

pgdbg> quit

PGI$ pgdbg test.exe

[GUI should open]
7

Hi,
this is the result of the test:

PGI Workstation 6.1-5 (x64)
PGI$ cd c:\test
PGI$ rm pg.dll
PGI$ rm test.exe test.pdb test.dwf
PGI$ ls
test.f90
PGI$ cat test.f90
print *, "hi"
endPGI$ pgf90 -g test.f90
PGI$ test.exe
 hi
PGI$ pgdbg -text test.exe
PGDBG 6.1-5 x86-64 (Workstation, 4 CPU)
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2006, STMicroelectronics, Inc. All Rights Reserved.
***Reading DWARFv2 Information.

The error message (see my first post) does not appear any more, but the system freezes after te message “***Reading DWARFv2 Information.”. Another window named “c:\PROGRA~1\PGI\win64\6.1-5\pgdbg1” -text test.exe is displayed, but is empty.

8

Hi B,

I finally talked with the right person and I think we found the problem. The command prompt’s screen buffer was assumed to have a width of 80 and the debugger will have problems if the default is set higher than 80. This problem has been corrected for the 6.2 release for 64-bit Windows currently scheduled for June 9th.

Open a command prompt and right mouse click on the icon in the upper left-hand corner. From the menu, select ‘Defaults’ and then the ‘Layout’ tab. Please adjust the ‘Screen Size Buffer’ and ‘Window Size’ Widths to be ‘80’.

Thanks,
Mat

9

Hi,
now works!
Thank you very much
b.