GNOME Bugzilla – Bug 353102
crash on Laplace effect
Last modified: 2006-09-23 13:59:32 UTC
Distribution: Ubuntu 6.06 (dapper) Package: camorama Severity: Normal Version: GNOME2.14.3 0.17 Gnome-Distributor: Ubuntu Synopsis: crash on Laplace effect Bugzilla-Product: camorama Bugzilla-Component: User Interface Bugzilla-Version: 0.17 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: Each time I try to activate the Laplace effect, camorama crashes Steps to reproduce the crash: 1. start camorama 2. deactivate the "Color correction" effect enabled by default 3. try to activate the "Laplace" effect Expected Results: Some video effect on the aplpication still running How often does this happen? Always Additional Information: This was tried on a Creative Live! webcam, with the spca5xx driver downloaded from Michel Xhaard site, version 20060501. Debugging Information: Backtrace was generated from '/usr/bin/camorama' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223894816 (LWP 18222)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 71073
Thread 1 (Thread -1223894816 (LWP 18222))
------- Bug created by bug-buddy at 2006-08-27 14:57 ------- Unknown version 0.17 in product camorama. Setting version to "unspecified".
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
I have recompiled the package locally with debugging symbols only for the application, not the other gnome libraries that trigger the callback. Here is the new stack trace. It seems the pointer to the image (first argument to the laplace call) is already corrupted at this level. (gdb) bt
+ Trace 71086
359 total1 = 0; 360 total2 = 0; 361 neighbours = 0; 362 363 image2 -= (x + 1) * 3; 364 total0 = total0 + image2[0]; 365 total1 = total1 + image2[1]; 366 total2 = total2 + image2[2]; 367 368 total0 = total0 + image2[3]; (gdb) list callbacks.c:653 648 threshold (cam->pic_buf, cam->x, cam->y, cam->dither); 649 } 650 651 if (func_state.laplace == TRUE) { 652 653 laplace (cam->pic_buf, cam->depth, cam->x, cam->y); 654 } 655 656 if (func_state.sobel == TRUE) { 657 sobel (cam->pic_buf, cam->x, cam->y); (gdb)
Turns out this is a duplicate of bug 156333. Thanks for filing the report and getting the other stack trace! *** This bug has been marked as a duplicate of 156333 ***