Bug 964154 - [abrt] vdrift-20120722-4.fc19: __memcpy_ssse3_back: Process /usr/bin/vdrift was killed by signal 11 (SIGSEGV)
[abrt] vdrift-20120722-4.fc19: __memcpy_ssse3_back: Process /usr/bin/vdrift w...
Product: Fedora
Classification: Fedora
Component: vdrift (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Gwyn Ciesla
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-05-17 07:36 EDT by Aritra Sasmal
Modified: 2015-02-17 10:15 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 10:15:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (2.45 MB, text/plain)
2013-05-17 07:37 EDT, Aritra Sasmal
no flags Details

  None (edit)
Description Aritra Sasmal 2013-05-17 07:36:14 EDT
Description of problem:
I simply launched the program and it crashed. I tried lauching from terminal as myself and root as well but it still crashed.

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        vdrift
crash_function: __memcpy_ssse3_back
executable:     /usr/bin/vdrift
kernel:         3.9.2-301.fc19.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __memcpy_ssse3_back at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:2280
 #1 memcpy at /usr/include/bits/string3.h:51
 #2 intel_upload_data at intel_buffer_objects.c:562
 #3 copy_array_to_vbo_array at brw_draw_upload.c:361
 #4 brw_prepare_vertices at brw_draw_upload.c:547
 #5 brw_emit_vertices at brw_draw_upload.c:574
 #6 brw_upload_state at brw_state_upload.c:501
 #7 brw_try_draw_prims at brw_draw.c:501
 #8 brw_draw_prims at brw_draw.c:589
 #9 vbo_handle_primitive_restart at ../../../src/mesa/vbo/vbo_exec_array.c:549
Comment 1 Aritra Sasmal 2013-05-17 07:37:23 EDT
Created attachment 749326 [details]
File: backtrace
Comment 2 Fedora End Of Life 2015-01-09 13:08:31 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2015-02-17 10:15:44 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.