David,
I have a core file for you. I'll send it to you off-list.
Bart
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpe
Martin Blapp wrote:
>
> To get a mimedefang corefile you may have to execute:
>
> # sysctl kern.sugid_coredump=1
Thank you, Martin. That seems to be exactly what I need. :-)
Waiting for the next segfault,
Bart
___
NOTE: If there is a disclaimer or ot
Hi,
To get a mimedefang corefile you may have to execute:
# sysctl kern.sugid_coredump=1
Martin
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.
Larry Starr wrote:
> Signal 11 (Segfault) is nearly always a Program bug (Accessing
> memory that is not allocated to the current process, frequently
> address zero, usually related to a pointer being used that has not
> been set correctly). It is, nearly, impossible that it points to a
> hardwar
> Signal 11 (Segfault) is nearly always a Program bug (Accessing memory that
is
> not allocated to the current process, frequently address zero, usually
> related to a pointer being used that has not been set correctly). It is,
> nearly, impossible that it points to a hardware (memory, overclo
On Tuesday 02 May 2006 15:51, Bjarte Husebø wrote:
> David F. Skoll wrote:
> > Doh... that's a segfault. You'll need to convince your system to
> > generate a core file to have any hope of diagnosing this.
>
> Thanks for your fast response. Unfortunately, analyzing core dumps is
> probably far bey
David F. Skoll wrote:
Well, if you can *get* a core file, I can help you out off-list.
Thank you very much for you offer, David. I really appreciate it!
I will try my best to figure out how to make the program generate a core
file. This is unknown territory, so I will have to dig around in
Bjarte Husebø wrote:
> Thanks for your fast response. Unfortunately, analyzing core dumps is
> probably far beyond my expertise. :-\
Well, if you can *get* a core file, I can help you out off-list.
Regards,
David.
___
NOTE: If there is a disclaimer or
Bjarte Husebø wrote:
Bad memory might be the reason for my problems - although I did run
Memtest86+ on it before I installed FreeBSD.
It might be worth the while to run another test.
If you can afford the time (i.e. if you've got another machine that can
handle its function for a while), let
David F. Skoll wrote:
Doh... that's a segfault. You'll need to convince your system to
generate a core file to have any hope of diagnosing this.
Thanks for your fast response. Unfortunately, analyzing core dumps is
probably far beyond my expertise. :-\
Cormack, Ken wrote:
If this is a li
> > May 2 18:06:02 amanda kernel: pid 19878 (mimedefang-multiple), uid 26:
> > exited on signal 11
> Doh... that's a segfault. You'll need to convince your system to
> generate a core file to have any hope of diagnosing this.
If this is a linux machine, I know of two circumstances under which yo
Bjarte Husebø wrote:
> May 2 18:06:02 amanda kernel: pid 19878 (mimedefang-multiple), uid 26:
> exited on signal 11
Doh... that's a segfault. You'll need to convince your system to
generate a core file to have any hope of diagnosing this.
Regards,
David.
___
12 matches
Mail list logo
