Re: stack trace without core
- From: Bin Chen <binary.chen@xxxxxxxxx>
- Date: Sat, 23 Jun 2007 00:00:54 -0000
On Jun 23, 2:33 am, RezaRob <Reza...@xxxxxxxxx> wrote:
On Jun 22, 7:04 am, Jasen <j...@xxxxxxxxxxx> wrote:It is an option because you can attach gdb to yourself when some
On 2007-06-22, RezaRob <Reza...@xxxxxxxxx> wrote:
Is there a way to generate a brief view of the stack without dumping
entire core?
attach gdb to the process?
This isn't an option because it's in "production mode" and only in the
event of an exception I need a stack trace.
exception occurs.
void segv_handler(int no)
{
int pid, status;
VoIPLog("segv_handler.");
char buf[128];
pid = getpid();
sprintf(buf, "/usr/bin/gdbserver :9988 --attach %d", pid);
pid = fork();
if (pid == 0) {
system(buf);
} else
::wait((int *)&status);
return;
}
.
- Follow-Ups:
- Re: stack trace without core
- From: Andrei Voropaev
- Re: stack trace without core
- References:
- stack trace without core
- From: RezaRob
- Re: stack trace without core
- From: Jasen
- Re: stack trace without core
- From: RezaRob
- stack trace without core
- Prev by Date: Re: stack trace without core
- Next by Date: collecting "oobs" message for user applications (WAS: Re: stack trace without core)
- Previous by thread: Re: collecting "oobs" message for user applications (WAS: Re: stack trace without core)
- Next by thread: Re: stack trace without core
- Index(es):
Relevant Pages
|
