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

Mantis Bug Tracker noreply at opencsw.org
Wed Feb 16 19:59:52 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:59 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
====================================================================== 

---------------------------------------------------------------------- 
 (0008800) phil (developer) - 2011-02-16 19:59
 https://www.opencsw.org/mantis/view.php?id=4690#c8800 
---------------------------------------------------------------------- 
Unfortunately, I cant share the particular example with you.
But have you tried debugging from core dumps?

If you compile the code below with cc (no -g), then dbx correctly says
crash occurred in main()
gdb is just completely lost, however.

Actually, even if you compile with gcc, the same is true.

so perhaps core dump analysis is broken.

--------------------

#include <stdio.h>

int main(){
        char *crashit;
        write(1,"This is a test\n",16);
        crashit=NULL;
        write(1,crashit,16);
        printf("a stringie %s ... \n",NULL);
        write(1,"This is A TEST\n",16);
}



More information about the bug-notifications mailing list