Operating System - HP-UX
1752624 Members
4767 Online
108788 Solutions
New Discussion

Cannot access memory at address 0xfffffe6f

 
ayelet_1
Occasional Contributor

Cannot access memory at address 0xfffffe6f

Hi Everyone,

I will start by saying that I am a system administrator and not a developer.
Be gentle with your answers (-:

One of the developers tried to debug our software and it failed with the errors:
GNU gdb 4.18-hppa-991112
Copyright 1998 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. This version of GDB is supported
for customers of Cygnus Solutions. Type "show warranty" for details.
This GDB was configured as "hppa1.1-hp-hpux11.00"...
(gdb) b main

Inferior GDB segmentation violation (core dumped)


Anyway, I tried to analyze the core file and got the following:

gdb) bt
#0 0xc01f45a0 in fseeko+0x68c () from /usr/lib/libc.2
#1 0x12414c in ISmRawFileIdentifier::_GetUNCKeyValue+0x44d4 ()
#2 0xc0191948 in _qfmul+0x320 () from /usr/lib/libc.2
#3 0x7ad1f958 in ?? ()
#4 0xc0191948 in _qfmul+0x320 () from /usr/lib/libc.2
Cannot access memory at address 0xfffffe6f


This is a C3600 workstation. Hpux 11.0. Physical: 1048576.

swapinfo -ma
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 1536 19 1517 1% 0 - 1 /dev/vg00/lvol2
dev 2048 18 2030 1% 0 - 1 /dev/vg00/lvol3
reserve - 64 -64
memory 571 245 326 43%
1 REPLY 1
Rick Beldin
HPE Pro

Re: Cannot access memory at address 0xfffffe6f

The probleem is likely that one of the parameters passed to fseeko() by _GGetUNCKeyValue() is incorrect or corrupt.

Since the code is built optimized, it is difficult to determine what the problem is without some significant effort. Get your developer to build the application and the libraries with debug turned on (-g or -g1) and turn off optimizations. See if you can then reproduce the problem.

I would also recommend getting the HP version of gdb since it has better support for unwinding the stack with shared libraries and knows about C++ idiosyncracies. You can get it here for free:

http://www.hp.com/go/wdb

Make sure that your aCC compiler is up to date and patched. Infomation about the C++ compiler is here:

http://www.hp.com/go/c++
Necessary questions: Why? What? How? When?