Getting random Emacs core dumps with gnus...

Getting random Emacs core dumps with gnus...

[Emerick Rogul]

Hi,

I've been getting random Emacs core dumps when I'm running gnus (it
happened with gnus 5.8.x from cvs and now with Oort 0.01).  Luckily, I
managed to save the core file when it happened today.  Issuing a
"where -v" when analyzing it in dbx gave me the following call stack:

=>[1] _libc_kill(0x0, 0xb, 0x102027ac, 0x0, 0x22134, 0x69238), at
0xfef9a790
  [2] fatal_error_signal(0xb, 0x0, 0xffbedbe0, 0xfefb8000, 0x0, 0x0),
at 0x69238
  [3] sigacthandler(0xb, 0x0, 0xffbedbe0, 0x0, 0x0, 0x0), at
0xfef99834
  ---- called from signal handler with signal 11 (SIGSEGV) ------
  [4] deactivate_process(0x2a553c, 0x1fbc00, 0x1fd400, 0x10f800, 0x0,
0x0), at 0x10dd38
  [5] send_process(0xffbedf90, 0x1, 0xffbee024, 0x6, 0x142364,
0x1fbc00), at 0x10fb1c

This doesn't really mean too much to me...  Should I follow this up
here, or would this be considered a more general Emacs problem (if so,
where should I report it)?

Any help would be appreciated.... :-)

Thanks,

-Emerick
-- 
-------------------------------------------------------------------------
Emerick Rogul             /\/     "how young are you, how old am i?
emerick@cs.bu.edu         /\/      let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats

Re: Getting random Emacs core dumps with gnus...

[Colin Walters]

Emerick Rogul <emerick@cs.bu.edu> writes:

> I've been getting random Emacs core dumps when I'm running gnus (it
> happened with gnus 5.8.x from cvs and now with Oort 0.01).

Does it still happen with Emacs 20.7?  Your headers say you're using
20.4.  If so, please file a bug report via 'M-x report-emacs-bug'.

Re: Getting random Emacs core dumps with gnus...

[Emerick Rogul]

Colin Walters writes:

: Emerick Rogul <emerick@cs.bu.edu> writes:
:: I've been getting random Emacs core dumps when I'm running gnus (it
:: happened with gnus 5.8.x from cvs and now with Oort 0.01).

: Does it still happen with Emacs 20.7?  Your headers say you're using
: 20.4.  If so, please file a bug report via 'M-x report-emacs-bug'.

I'll try to give it a test with 20.7.  Thanks for the advice!

-Emerick
-- 
-------------------------------------------------------------------------
Emerick Rogul             /\/     "how young are you, how old am i?
emerick@cs.bu.edu         /\/      let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats

Re: Getting random Emacs core dumps with gnus...

[Hans de Graaff]

On 02 Jan 2001, Emerick Rogul wrote:
> 
> =>[1] _libc_kill(0x0, 0xb, 0x102027ac, 0x0, 0x22134, 0x69238), at
> 0xfef9a790
>   [2] fatal_error_signal(0xb, 0x0, 0xffbedbe0, 0xfefb8000, 0x0,
>   0x0),
> at 0x69238
>   [3] sigacthandler(0xb, 0x0, 0xffbedbe0, 0x0, 0x0, 0x0), at
> 0xfef99834
>   ---- called from signal handler with signal 11 (SIGSEGV) ------
>   [4] deactivate_process(0x2a553c, 0x1fbc00, 0x1fd400, 0x10f800,
>   0x0,
> 0x0), at 0x10dd38
>   [5] send_process(0xffbedf90, 0x1, 0xffbee024, 0x6, 0x142364,
> 0x1fbc00), at 0x10fb1c
> 
> This doesn't really mean too much to me...  Should I follow this up
> here, or would this be considered a more general Emacs problem (if
> so, where should I report it)?

This might also be a hardware problem. Perhaps one of your memory
chips has gone south? If it happens a lot in different routines than
memory corruption is a pretty good guess.

Hans