topic Re: GDB error in Operating System - HP-UX

GDB error

ayelet_1 — Wed, 07 Jan 2004 11:21:29 GMT

Hi All,

Iâ m receiving error message when running GDB.

Does someone know these errors? (Please donâ t recommend to work with WDB...)

(gdb)Program terminated with signal SIGKILL, Killed.
The program no longer exists.
You can't do that without a process to debug.

Thanks in advanced,
Ayelet

Re: GDB error

Olivier Drouin — Wed, 07 Jan 2004 11:36:30 GMT

the program you're trying to grab crashed.

find the core file then:

gdb -c core_file /path/to/binary

Re: GDB error

ayelet_1 — Wed, 07 Jan 2004 11:51:08 GMT

There is no core file...

Ayelet

Re: GDB error

ranganath ramachandra — Fri, 09 Jan 2004 01:35:47 GMT

(i am not very sure about this, but ...)

if you are getting this message as soon as you run gdb (perhaps even without any arguments), please check what exists in your .gdbinit or ~/.gdbinit file. also post your gdb command.

the message is telling you that the program being debugged was killed due to a SIGKILL signal - as if someone did a 'kill -9' on it.
this is possible if
1. you are trying to attach to an already running process which got killed by itself some other process
2. you started the process from within gdb but the process killed itself

if yours is the first case, try starting the process from within gdb. if it is the second case, try setting a breakpoint early in the process (say on "main" if you can).

perhaps we can make out more from the output of chatr on the executable and the tusc trace of the process.

Re: GDB error

Elmar P. Kolkman — Fri, 09 Jan 2004 02:23:38 GMT

One other possibility, though not very likely: some other session removed the executable and replaced it with a new one.

This might happen if you're not the only one working on it, for instance.

You can check this by looking at the timestamp of the executable after this happens.

Perhaps copying the executable and running gdb on this copy could help.