Re: Dumping a core from inside of process

Artem 'Zazoobr' Ignatjev wrote: Hello, hackers I'm writing some program, which dlopens() a lot of shared objects, and can do nasty things to it's own memory. Some day I decided to trap fatal memory signals, like SIGILL, SIGBUS and SIGSEGV, and wrote a handler for these, which swears with bad

Re: Dumping a core from inside of process

Look for abort() or SIGABRT. On 21 Aug 2003 21:57:41 + Artem 'Zazoobr' Ignatjev [EMAIL PROTECTED] wrote: Hello, hackers I'm writing some program, which dlopens() a lot of shared objects, and can do nasty things to it's own memory. Some day I decided to trap fatal memory signals, like

Re: Dumping a core from inside of process

At Thu, 21.08.2003, 22:05, Lev Walkin wrote: Artem 'Zazoobr' Ignatjev wrote: Hello, hackers I'm writing some program, which dlopens() a lot of shared objects, and can do nasty things to it's own memory. Some day I decided to trap fatal memory signals, like SIGILL, SIGBUS and SIGSEGV,

Re: Dumping a core from inside of process

At Thu, 21.08.2003, 22:02, Alexander Kabaev wrote: Look for abort() or SIGABRT. Thanks so far for you and Lev.. Is there the way to specify struct sigcontext to it? I still wish to have `correct' registers values to be written into coredump, those that were when signal happened, and not that were

Re: Dumping a core from inside of process

Artem 'Zazoobr' Ignatjev wrote: At Thu, 21.08.2003, 22:05, Lev Walkin wrote: Artem 'Zazoobr' Ignatjev wrote: Hello, hackers I'm writing some program, which dlopens() a lot of shared objects, and can do nasty things to it's own memory. Some day I decided to trap fatal memory signals, like

Re: Dumping a core from inside of process

On Thu, Aug 21, 2003 at 10:12:49PM + or thereabouts, Artem 'Zazoobr' Ignatjev wrote: At Thu, 21.08.2003, 22:02, Alexander Kabaev wrote: Look for abort() or SIGABRT. Thanks so far for you and Lev.. Is there the way to specify struct sigcontext to it? I still wish to have `correct'