core debugging problen

core debugging problen

Post by Satish N » Thu, 08 Apr 1999 04:00:00

I have a problem in debugging the cores. The scenario is this.

0. There is a process which is running as a deamon and will be started
during the
0. This deamon will fork and exec another executable. Since the new
process is the child of the the deamon, it will also have the properties

of the deamon and hence it will also be a deamon.
0. Now, if the child parent coredumps, the real problem arises. I am not

able to open the core file. Suppose, the path of the executable is
/opt/CCM/bin, then the deamon will fork and call exec with the options
giving the complete path of the executable (ex: /opt/CCM/bin/sc_sms)
with arguements as usual.
0. When I try to open the core file with the de* (xdb) it complains

"unknown symbol  /opt.

If I run the executable alone, then I will get a very good core. I don't

know the reason for this. Please, help me in this regard



1. Redhat 4.0 Can't debug core files

Hello... I've upgraded to Redhat 4.0 (Kernel 2.0.18) and have found that
I cannot debug core files, gdb (version 4.16) says that it does not
recognise the file type.

Is there another debugger that I can use, if so where is it ?



2. GUI Newsreaders-Offline/Online in Linux

3. Help needed debugging with a core file

4. SURVEY: Graphics card benchmarks under XFree86 (12 Sep 95)

5. 1 * zTtNsCtEm-core file debugging...

6. Fujitsu Servers Running Solaris???

7. Debug Core

8. Welcome_arcade and .rsc files

9. help needed to debug core dumps

10. Core debug

11. How to debug a core file

12. Debugging core-dumps under AIX 3.2

13. debugging core files