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 620362 - mp3 extraction crashes if year string is NULL before using atoi() with libenca enabled
mp3 extraction crashes if year string is NULL before using atoi() with libenc...
Status: RESOLVED FIXED
Product: tracker
Classification: Core
Component: Extractor
0.8.x
Other Linux
: Normal critical
: ---
Assigned To: tracker-extractor
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2010-06-02 14:15 UTC by Deji Akingunola
Modified: 2010-06-24 08:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Crash backtace (64.05 KB, text/plain)
2010-06-02 14:15 UTC, Deji Akingunola
Details

Description Deji Akingunola 2010-06-02 14:15:26 UTC
Created attachment 162543 [details]
Crash backtace

Originally reported at https://bugzilla.redhat.com/show_bug.cgi?id=596764 .
Comment 1 Fabio Durán Verdugo 2010-06-02 20:42:30 UTC
paste here the backtrace


[New Thread 2612]
[New Thread 2619]
[New Thread 2624]
[New Thread 2626]
[New Thread 2627]
[New Thread 2632]
[New Thread 2633]
[New Thread 2634]
[New Thread 2635]
[New Thread 2636]
[New Thread 2638]
[New Thread 2639]
[New Thread 2640]
[New Thread 2644]
[New Thread 2645]
[New Thread 2651]
[New Thread 2669]
[New Thread 2670]
[New Thread 2679]
[New Thread 2680]
Core was generated by `/usr/libexec/tracker-extract'.
Program terminated with signal 11, Segmentation fault.

Thread 1 (Thread 2612)

  • #0 ____strtol_l_internal
    at ../stdlib/strtol_l.c line 298
  • #1 atoi
  • #2 get_id3
  • #3 extract_mp3
  • #4 get_file_metadata
  • #5 tracker_extract_get_metadata
  • #6 invoke_object_method
    at dbus-gobject.c line 1470
  • #7 object_registration_message
    at dbus-gobject.c line 1622
  • #8 _dbus_object_tree_dispatch_and_unlock
    at dbus-object-tree.c line 856
  • #9 dbus_connection_dispatch
    at dbus-connection.c line 4492
  • #10 message_queue_dispatch
    at dbus-gmain.c line 101
  • #11 g_main_dispatch
    at gmain.c line 1960
  • #12 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #13 g_main_context_iterate
    at gmain.c line 2591
  • #14 IA__g_main_loop_run
    at gmain.c line 2799
  • #15 main
    at tracker-main.c line 466

Comment 2 Aleksander Morgado 2010-06-07 10:29:57 UTC
(In reply to comment #0)
> 
> Originally reported at https://bugzilla.redhat.com/show_bug.cgi?id=596764 .

It seems the original bugreport in RH is not the proper one...
Comment 3 Martyn Russell 2010-06-14 11:37:01 UTC
Can you attach the file that created this crash so we can test it here please?
Comment 4 Deji Akingunola 2010-06-14 16:50:24 UTC
(In reply to comment #2)
> (In reply to comment #0)
> > 
> > Originally reported at https://bugzilla.redhat.com/show_bug.cgi?id=596764 .
> 
> It seems the original bugreport in RH is not the proper one...

Sorry it is at https://bugzilla.redhat.com/show_bug.cgi?id=596839
Comment 5 Deji Akingunola 2010-06-15 15:54:55 UTC
File forwarded as PM for privacy reasons. Original reporter doesn't want the file posted on the web.
Comment 6 Aleksander Morgado 2010-06-23 20:07:27 UTC
(In reply to comment #5)
> File forwarded as PM for privacy reasons. Original reporter doesn't want the
> file posted on the web.

Could you email that file to me?
Comment 7 Martyn Russell 2010-06-24 08:08:07 UTC
(In reply to comment #6)
> (In reply to comment #5)
> > File forwarded as PM for privacy reasons. Original reporter doesn't want the
> > file posted on the web.
> 
> Could you email that file to me?

Done.

(In reply to comment #5)
> File forwarded as PM for privacy reasons. Original reporter doesn't want the
> file posted on the web.

Thank you for forwarding the file, reproducible only with libenca enabled.

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.