Bug 1034903

Summary: [abrt] squidGuard-1.4-17.fc19: memcpy: Process /usr/bin/squidGuard was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: fishears <f1she4rs>
Component: squidGuardAssignee: Gwyn Ciesla <gwync>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: gwync, itamar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/496f012ba50077c442576a229c59e570d87fbae6
Whiteboard: abrt_hash:4d1bb9190315b96443fcd75e6a35686fed1255cc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-01 10:09:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description fishears 2013-11-26 16:54:20 UTC 
Description of problem:
simply entered the command "squidGuard" in the terminal (as root)
it segfault's every time
squid itself is installed and working

Version-Release number of selected component:
squidGuard-1.4-17.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        squidGuard
crash_function: memcpy
executable:     /usr/bin/squidGuard
kernel:         3.11.9-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 memcpy at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:1771
 #2 sgDbUpdate at sgDb.c:513
 #3 sgSourceUser at sg.y:593
 #4 yyparse at sg.y:225
 #5 sgReadConfig at sg.y:385

Potential duplicate: bug 965763
Comment 1 fishears 2013-11-26 16:54:29 UTC 
Created attachment 829377 [details]
File: backtrace
Comment 2 fishears 2013-11-26 16:54:33 UTC 
Created attachment 829378 [details]
File: cgroup
Comment 3 fishears 2013-11-26 16:54:36 UTC 
Created attachment 829379 [details]
File: core_backtrace
Comment 4 fishears 2013-11-26 16:54:40 UTC 
Created attachment 829380 [details]
File: dso_list
Comment 5 fishears 2013-11-26 16:54:44 UTC 
Created attachment 829381 [details]
File: environ
Comment 6 fishears 2013-11-26 16:54:47 UTC 
Created attachment 829382 [details]
File: exploitable
Comment 7 fishears 2013-11-26 16:54:51 UTC 
Created attachment 829383 [details]
File: limits
Comment 8 fishears 2013-11-26 16:54:55 UTC 
Created attachment 829384 [details]
File: maps
Comment 9 fishears 2013-11-26 16:54:58 UTC 
Created attachment 829385 [details]
File: open_fds
Comment 10 fishears 2013-11-26 16:55:03 UTC 
Created attachment 829386 [details]
File: proc_pid_status
Comment 11 fishears 2013-11-26 16:55:07 UTC 
Created attachment 829387 [details]
File: var_log_messages
Comment 12 fishears 2013-12-01 10:09:12 UTC 
Sorry. I've done some work on my config files and now squidGuard does not segfault. The segfault that occurs with the default configuration is not helpful to users but with correct configuration everything seems to work.