[nos-bbs] Segmentation Fault - with back trace

SP2L SP2L at sp2l.ampr.org
Mon Oct 23 11:39:07 EDT 2017


Hello Ray.


I do understand your concern in that matter.

Remotely it is really difficult to cure such issue,
not knowing vital environment details of thesystem.

But...before you go further and abandon Debian,
run the following from command line (it's safe!):

- apt-get -f install
   (Fix; attempt to correct a system with broken dependencies in place)
- apt-get check
   (check is a diagnostic tool; it updates the package cache
    and checks for broken dependencies)
- apt-get update
   (update is used to resynchronize the package index files from their 
sources)
- apt-get autoremove
   (autoremove is used to remove packages that were automatically installed
    to satisfy dependencies for other packages and are now no longer needed)


Next, if you're not afraid of any updates to the system,run also:
- apt-get upgrade
   (upgrade is used to install the newest versions
    of all packages currently installed)

Above five commands I run almost on every login
to my systems, just in case something went askew.


However, YMMV...

Best regards.
Tom - SP2L



On 22/10/17 17:47, Ray Quinn wrote:
> On 10/11/2017 4:14 AM, sp2l wrote:
>> Hello Ray.
>>
>>
>> This seem _very_ similar to your issue reported on Aug 20th,
>> with _ exactly_  the same package as before:
>>
>>   glibc-source_2.19-18+deb8u10_all.deb
>>
>>   ( 
>> glibc-2.19.tar.xz/utar://glibc-2.19/sysdeps/unix/sysv/linux/i386/makecontext.S 
>> )
>>
>>
> Sorry for the delay. I have been working the fires again. This last 
> time north of San Francisco in and near Santa Rosa and Calistoga, 
> California.
>
> I don't know how to resolve this. The file and package is there. I 
> understand you are trying to help, but I don't know what to do from 
> here. Sometimes it SEGFAULTS within one minute, other times it runs 
> for days.
>
> The latest along with the backtrace is different that the previous one 
> at the bottom:
>
> Program received signal SIGSEGV, Segmentation fault.
> __strlen_sse2_bsf () at 
> ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50
> 50      ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S: No such file 
> or directory.
>
> The file is here:
>
> @nos:~# locate strlen-sse2-bsf.S
> /usr/src/glibc/debian/glibc-2.19/sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S 
>
>
>
>
> (gdb) bt
> #0  __strlen_sse2_bsf () at 
> .../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50
>
> Does the :50 mean line 50 in that file?
>
> #1  0x080b51d2 in dn_compress (msg=0x9f7d658 "GE\320\004/ ", 
> dp=0x8766180,
>     cp=0x9f7d71d "", name=0x0) at domhdr.c:359
> #2  0x080b5729 in htondomain (dhdr=0x867ffe8, buffer=0x9f7d658 
> "GE\320\004/ ",
>     buflen=4352) at domhdr.c:507
> #3  0x080b4199 in proc_query (unused=0, d=0x8774d58, b=0x867ffe8)
>     at domain.c:2517
> #4  0x080a439a in _kicker (func=0x80b3f3c <proc_query>, iarg=0,
>     parg1=0x8774d58, parg2=0x867ffe8) at ksubr.c:142
> #5  0xb73b891b in makecontext ()
>     at ../sysdeps/unix/sysv/linux/i386/makecontext.S:87
>
>
> @nos:~# locate makecontext.S
> /usr/src/glibc/debian/glibc-2.19/sysdeps/unix/sysv/linux/i386/makecontext.S 
>
>
> #6  0x080b3f3c in domainsuffix (dname=0x8774d58 "") at domain.c:2398
> #7  0x00000000 in ?? ()
>
> Perhaps I should abandon Debian for another flavor and put it back in 
> a VM. Any suggestions on any of it? Anyone?
>
> Going to take a break from it for now. Going to the repeater site 
> where the TNC's and radios are located. I need to reset the TCP/IP 
> <>Serial device and tune up before winter sets in.
>
>>
>> -----Oryginalna wiadomość----- From: Ray Quinn
>> Sent: Sunday, October 8, 2017 10:37 PM
>> To: nos-bbs at tapr.org
>> Subject: [nos-bbs] Segmentation Fault - with back trace
>>
>> On 10/4/2017 5:58 PM, Ray Quinn wrote:
>>> Below is the latest Segmentation Fault using the latest available 
>>> code via RSYNC. Running Debian 8. I have no idea where to start...
>>>
>>>
>> This is the complete error:
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x080c475d in nr4sframe (dest=0x83b3c68 "X\356:\b@=;\b", hdr=0x0,
>> bp=0x0) at nr4.c:348
>> 348             nr3output(dest, n4b);
>> (gdb) bt
>> #0  0x080c475d in nr4sframe (dest=0x83b3c68 "X\356:\b@=;\b", hdr=0x0,
>> bp=0x0) at nr4.c:348
>> #1  0x080c6d17 in nr_poll_resp (targ=0x83b62f8) at nr3.c:874
>> #2  0x080a09c4 in timerproc (i=0, v1=0x0, v2=0x0) at timer.c:59
>> #3  0x080a439a in _kicker (func=0x80a090e <timerproc>, iarg=0,
>> parg1=0x0, parg2=0x0) at ksubr.c:142
>> #4  0xb737c91b in makecontext () at
>> ../sysdeps/unix/sysv/linux/i386/makecontext.S:87
>> #5  0x080a090e in bitbucket (ifp=0x0, bp=0x0) at iface.c:837
>> #6  0x00000000 in ?? ()
>> (gdb)
>>
>>
>>
>>
>
>




More information about the nos-bbs mailing list