After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 463891 - crash on record second track
crash on record second track
Status: RESOLVED DUPLICATE of bug 329922
Product: gnome-media
Classification: Deprecated
Component: Gnome-Sound-Recorder
2.18.x
Other Linux
: Normal critical
: ---
Assigned To: gnome media maintainers
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-06 06:59 UTC by Yang Hong
Modified: 2007-09-06 19:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Yang Hong 2007-08-06 06:59:36 UTC
step to represent:

1. press "record" to record first track
2. press "stop", then save the track or not
3. press "record" to record secound track

gsr crashed

backtrace:

Program received signal SIGSEGV, Segmentation fault.

Thread NaN (LWP 5396)

  • #0 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #1 record_input_changed_cb
    at gsr-window.c line 1792
  • #2 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #3 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #4 ??
    from /usr/lib/libgobject-2.0.so.0
  • #5 ??
  • #6 ??

in the gsr-window.c:1792 record_input_changed_cb ()

text = gtk_combo_box_get_active_text (input); got a 0x0 return value, then the 'text' was used to compare with t->label with strcmp, then crashed.

Why the record_input_changed_cb() was called when I start to record second track? I reviewed the code, I guess it is called by the "Changed" signal emited by the 

gtk_combo_box_set_active (GTK_COMBO_BOX (window->priv->input), i - 1);

in the

fill_record_input (GSRWindow *window) from gsr-window.c:1812

which called from 

record_cb (GtkAction *action,
           GSRWindow *window)
at gsr-window.c:1267 ?
Comment 1 Bastien Nocera 2007-09-06 19:17:14 UTC
Fixed as part of bug 329922.

*** This bug has been marked as a duplicate of 329922 ***