arpon crashed with SIGSEGV in pthread_kill()

Bug #1207508 reported by daniel CURTIS
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
arpon (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi. Today, after turning on computer, ArpON application crashed. On a panel appeared a sign about crash, but ArpON seems to work okay:

,-----[ check arpon ]
| /etc/init.d/arpon status [OK]
`-----

ArpON also logs events to a '/var/log/arp/arpon' file. I did not changed default file ('/etc/default/arpon'), because it already was set for use a DHCP protocol. Anyway, here is a more info about mentioned crash:

* ProblemType: Crash
* Arch: i386
* DistroRelease: Xubuntu 12.04.2
* Tags: precise
* ApportVersion: 2.0.1-0ubuntu17.3
* NonfreeKernelModules: nvidia
* Package: arpon 2.0-2.1
* Uname 3.2.0-51.77-generic-pae 3.2.48
* Signal: 11

And here is more detailed info:

,-----[ SegvAnalysis ]
| Segfault happened at: 0xb76cfa79 <pthread_kill+9>: mov 0x68(%eax),%ecx
| PC (0xb76cfa79) ok
| source "0x68(%eax)" (0xb7519ba8) not located in a known VMA region (needed readable region)!
| destination "%ecx" ok
| Stack memory exhausted (SP below stack segment)
`-----

,-----[ lsb_release -a ]
| No LSB modules are available.
| Distributor ID: Ubuntu
| Description: Ubuntu 12.04.2 LTS
| Release: 12.04
| Codename: precise
`-----

Also on all Thread Stacktrace available in a crash report, there is 'No symbol table info available.' for all Threads. As we already know, there is available a new version of ArpON - 2.7. While in each Ubuntu version/release still is 2.0-2.1.

daniel CURTIS (anoda)
affects: cups (Ubuntu) → arpon (Ubuntu)
Revision history for this message
daniel CURTIS (anoda) wrote :

Hi, today ArpON crashes once again. I've decided to stop using such important utility, until it will get fixed/updated. Thanks.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in arpon (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.