[bug-notifications] [gdb 0004690]: "Can't read pathname for load map"

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4690 
====================================================================== 
Reported By:                phil
Assigned To:                pfelecan
====================================================================== 
Project:                    gdb
Issue ID:                   4690
Category:                   regular use
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2011-02-15 19:33 CET
Last Modified:              2011-02-16 10:00 CET
====================================================================== 
Summary:                    "Can't read pathname for load map"
Description: 
I just tried loading up a program with the new gdb, on a sol9 system
(5.9 Generic_122300-02 sun4u sparc SUNW,UltraAX-i2)

and got the error in the subject line.

This seems to be exactly like 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=248898

It makes debugging useless: no stack trace possible.

the problem there is that they suggest "install libc6-dbg", which fixed
their problem.
I have no idea what we should do on Solaris, unfortunately.
btw, I read the README.CSW file, and my shell is /bin/ksh
====================================================================== 

---------------------------------------------------------------------- 
 (0008797) pfelecan (manager) - 2011-02-16 10:00
 https://www.opencsw.org/mantis/view.php?id=4690#c8797 
---------------------------------------------------------------------- 
The reason for which the Debian maintainer gives that advice is that the
failure of the user program happens in the libc6 and for having an "usable"
stack trace for that portion of code he needs the debugging symbols of the
library itself.

If you give me a simple example which I can reproduce I can look into it.