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

Mantis Bug Tracker noreply at opencsw.org
Wed Feb 16 19:30:26 CET 2011


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 19:30 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
====================================================================== 

---------------------------------------------------------------------- 
 (0008799) pfelecan (manager) - 2011-02-16 19:30
 https://www.opencsw.org/mantis/view.php?id=4690#c8799 
---------------------------------------------------------------------- 
It doesn't says exactly that. It says that for the code which is the
probable cause of the core it has no symbols. It's not unusual that a
program fails in the startup code, even before main().

gdb itself was compiled with gcc, release 4.

Again, if you provide me an example of code which exercises the behavior
that you describe I will look into it. Otherwise all that I can say is that
"it works for me".



More information about the bug-notifications mailing list