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

Mantis Bug Tracker noreply at opencsw.org
Wed Jul 25 08:58:43 CEST 2012


The following issue has been CLOSED 
====================================================================== 
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:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2011-02-15 19:33 CET
Last Modified:              2012-07-25 08:58 CEST
====================================================================== 
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
====================================================================== 

---------------------------------------------------------------------- 
 (0010054) pfelecan (manager) - 2012-07-25 08:58
 https://www.opencsw.org/mantis/view.php?id=4690#c10054 
---------------------------------------------------------------------- 
The freshly released package containing version 7.4.1 should correct this.
Anyway, feedback is welcome and if the issue persists it can be re-opened.



More information about the bug-notifications mailing list