Re: [Tlf-devel] Re: TLF 0.8.19

[Mike Tatum]

Hi Joop,

I've not done any programming for many years ...
I supposed now is a good time to revisit those good ole days :_))

MikeT ...

On Wednesday 23 April 2003 7:11 pm, Joop Stakenborg wrote:
> Mike Tatum wrote:
> > Gents,
> >
> > I removed all the hashed lines from the logcfg.dat file but it still
> > reported:
> >
> > close(3)                                = 0
> > munmap(0x30015000, 4096)                = 0
> > rt_sigaction(SIGTSTP, {SIG_IGN}, {0xff5c6c0, [], SA_RESTART}, 8) = 0
> > _newselect(0x1, 0x7ffff878, 0, 0, 0x7ffff8f8) = 0
> > _newselect(0x1, 0x7ffff878, 0, 0, 0x7ffff8f8) = 0
> > write(1, "\r\nreading configuration data", 28) = 28
> > rt_sigaction(SIGTSTP, {0xff5c6c0, [], SA_RESTART}, NULL, 8) = 0
> > open("logcfg.dat", O_RDONLY)            = 3
> > fstat(3, {st_mode=S_IFREG|0644, st_size=450, ...}) = 0
> > mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
> > = 0x30015000
> > read(3, "EDITOR=vi\nCALL=M0AWS\nCONTEST=qso"..., 4096) = 450
> > --- SIGSEGV (Segmentation fault) ---
> > +++ killed by SIGSEGV +++
> >
> >
> > Has anyone seen this problem on the Intel platform or is this PPC
> > specific ?
>
> Hello Mike,
>
> don't think it is PPC specific (it would surprise me).
> Do you know how to use a debugger (gdb), this might be helpful
> in tracing the error.
>
> > Regards,
> >
> > MikeT ...
> > M0AWS
>
> Joop PA4TU