> > > Can you still try to get a core file, and send that to me (gzipped)?
> >
> > I couldn't find a core file. Where should it end up --- in the
> > directory that inc was run from? It's not there. (Nor could I find
> > it anywhere else.)
> >
> > > If inc also segfaults if you run it with -file, you can try copying
> > > /usr/bin/mh/inc to your own directory (so it'll lose its setgid bit) and
> > > run it as
> > >
> > > strace -o inc.trace ./inc -silent -file mailbox +tmp2
> >
> > Okay, I've done this and included inc.trace, using X-uuencode. I'll also
> > include the mail file again using X-uuencode, just in case last time someth
> ing> was mucked up in the file transfer.
>
> The trace file was useful, but not enough for me to determine where things
> go wrong. In order to create a core dump file, you probably have to do
>
> ulimit -c unlimited (if you're using the bash shell)
> limit coredumpsize unlimited (if you're using the tcsh shell)
>
> And then run inc again (strace is not needed). The file is named core, and
> is placed in the directory you ran inc from. The same rule applies here for
> privileged processes.
I did the "ulimit -c unlimited" (I'm using bash) and then ran inc
again, but still no core file!! Any more ideas on this?
> Thanks a lot for your cooperation in tracking down this bug!
No thank you. Anything to get rid of this bug will be great.
Cheers,
Mark.
_/~~~~~~~~\___/~~~~~~\____________________________________________________
____/~~\_____/~~\__/~~\__________________________Mark_Phillips____________
____/~~\_____/~~\[EMAIL PROTECTED]
____/~~\HE___/~~\__/~~\APTAIN_____________________________________________
____/~~\______/~~~~~~\____________________________________________________
__________________________________________________________________________
"They told me I was gullible ... and I believed them!"
