程序为什么coredump？

hnyanhui

我在hp 11下写了一个动态库的程序，运行正常，但退出时coredump。请各位大侠指点。
    我的动态库程序libtest.cpp如下：
  

1. 
   
2. #include <iostream.h>;
   
3. 
   
4. extern "C" {
   
5. int memory (  )
   
6. {
   
7.         cout << "Enter Share Lib" << endl;
   
8.         return 1;
   
9. }
   
10. 
    
11. }

复制代码

我的主程序main.cpp如下：

1. 
   
2. #include <stdio.h>;
   
3. #include <dl.h>;
   
4. #include <stdlib.h>;
   
5. #include <unistd.h>;
   
6. 
   
7. int main ( int argc , char **argv )
   
8. {               
   
9.         shl_t hndl;
   
10.         int  (*memory)();
    
11.        
    
12.         if ((hndl = shl_load("/home/test/yh/stl/bas1/libtest.sl",BIND_IMMEDIATE| BIND_NONFATAL, 0L)) == NULL)
    
13.                    perror("shl_load: error loading libtest.sl"), exit(1);
    
14.                   
    
15.            if (shl_findsym(&hndl, "memory", TYPE_PROCEDURE,(void *) &memory))
    
16.                 perror("shl_findsym: error loading libtest.sl"), exit(1);
    
17.                   
    
18.            printf("ret := %d\n" , (*memory)() );
    
19.                           
    
20.         shl_unload(hndl);
    
21. 
    
22.         printf("close share lib\n");
    
23.         exit(0);
    
24. }
    
25. 
    

复制代码

编译命令如下：

1. 
   
2. aCC +DA2.0W -c +Z  libtest.cpp
   
3. ld -E -b  -o  libtest.sl libtest.o
   
4. aCC +DA2.0W main.cpp -o main -ldld
   

复制代码

运行结果如下：

1. 
   
2. $ ./main
   
3. Enter Share Lib
   
4. ret := 1
   
5. close share lib
   
6. Memory fault(coredump)
   

复制代码

请问这是为什么？

蓝色键盘

把main的最后的exit(0);换成return 0;看看core码？


如果还core把core文件用gdb调试的信息贴上来

的确有点变态！

fightxxx

内存访问错误！看看有没有什么地方用错指针，或者是字符串后“\0”的问题

hnyanhui

蓝色键盘，我按照你说的做了，还是一样。
    下面时调试信息
  

1. 
   
2. gdb -c core
   
3. Detected 64-bit corefile.
   
4. Invoking /opt/langtools/bin/gdb64.
   
5. HP gdb 3.1.5 for PA-RISC 2.0 (wide), HP-UX 11.00.
   
6. Copyright 1986 - 2001 Free Software Foundation, Inc.
   
7. Hewlett-Packard Wildebeest 3.1.5 (based on GDB) is covered by the
   
8. GNU General Public License. Type "show copying" to see the conditions to
   
9. change it and/or distribute copies. Type "show warranty" for warranty/support.
   
10. 
    
11. Reading symbols from main...(no debugging symbols found)...done.
    
12. Core was generated by `main'.
    
13. Program terminated with signal 11, Segmentation fault.
    
14. (no debugging symbols found)...
    
15. warning: The shared libraries were not privately mapped; setting a
    
16. breakpoint in a shared library will not work until you rerun the program.
    
17. 
    
18. (no debugging symbols found)...
    
19. (no debugging symbols found)...(no debugging symbols found)...
    
20. (no debugging symbols found)...(no debugging symbols found)...
    
21. (no debugging symbols found)...(no debugging symbols found)...
    
22. (no debugging symbols found)...#0  0xc000000000064d60 in __cxxTerm+0x18 ()
    
23.    from /usr/lib/pa20_64/libCsup.2
    
24. (gdb) where
    
25. #0  0xc000000000064d60 in __cxxTerm+0x18 () from /usr/lib/pa20_64/libCsup.2
    
26. #1  0xc000000000184ea0 in exit+0x88 () from /usr/lib/pa20_64/libc.2
    
27. #2  0xc000000000017834 in UT_exit+0x2c () from /usr/lib/pa20_64/dld.sl
    
28. #3  0xc00000000001861c in exit+0x14 () from /usr/lib/pa20_64/dld.sl
    
29. #4  0xc0000000000218c0 in $START$+0xb0 () from /usr/lib/pa20_64/dld.sl
    
30. Error accessing memory address 0x0: Invalid argument.
    
31.    

复制代码

请问这是什么回事？

蓝色键盘

no debugging symbols found

编译的时候-g加上调试信息。

Program terminated with signal 11, Segmentation fault


检查包含的头文件和连接的库