Re: Program suddenly gets killed
From: LaBird (not_my_mail_at_mail.com)
Date: 09/17/04
- Next message: Andy Fraser: "Re: Newbie and Debian."
- Previous message: roodwriter_at_core.com: "Re: Formatting Posts With VI"
- In reply to: Sybren Stuvel: "Re: Program suddenly gets killed"
- Next in thread: Andrea Raimondi: "Re: Program suddenly gets killed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 17 Sep 2004 19:10:11 +0800
Thanks, but what it gives is just like this:
Program terminated with signal SIGKILL, Killed.
The program no longer exists.
And then I cannot get where it is killed by using "where".
In such case, can I know which statement in the code causes the problem?
Best Regards,
LaBird (Benny).
"Sybren Stuvel" <sybrenUSE@YOURthirdtower.imagination.com> wrote in message
news:slrnckl6h1.s7s.sybrenUSE@sybren.thirdtower.com...
> LaBird enlightened us with:
> > I have a C++ program running on Linux that does a lot of disk
> > read/write and (virtual) memory operations (like mmap). But
> > sometimes when it runs, it encounters a "Killed" signal and is
> > killed midway through the execution.
>
> Run it via 'gdb' to debug.
>
> Sybren
> --
> The problem with the world is stupidity. Not saying there should be a
> capital punishment for stupidity, but why don't we just take the
> safety labels off of everything and let the problem solve itself?
- Next message: Andy Fraser: "Re: Newbie and Debian."
- Previous message: roodwriter_at_core.com: "Re: Formatting Posts With VI"
- In reply to: Sybren Stuvel: "Re: Program suddenly gets killed"
- Next in thread: Andrea Raimondi: "Re: Program suddenly gets killed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|