Re: [Gtkpod-devel] Segmentation fault with gtkpod

[Jorg S. <Jor...@gm...>]

James Steward wrote:
> On Tue, 2007-10-23 at 12:02 -0700, John Felts wrote:
>> It went to the very last song, and then hung. Eventually the window
>> closed on its own, and now gtkpod will not open while the ipod is
>> connected. It opens, then closes immediately. Here's the error from a
>> terminal :
>>
>> ** (gtkpod:6331): CRITICAL **: ipod_parse_artwork_db: assertion `itdb'
>> failed
>> Segmentation fault (core dumped)
>>
>> Any ways to fix this?
> 
> I don't know how to fix it, and I don't know if this is a known bug -
> although I should think your email would have been replied to by now if
> it was.
> 
> What I can suggest, is that you try a little debugging to help the
> developers understand the problem a little better.
> 
> Did you build gtkpod and libgpod from source?
> If no, then the options are limited (examining the core dump), but if
> yes, then see if you can rebuild them with debugging turned on (-g) and
> run gtkpod under gdb.  Gdb will trap the oops, and you can type "where"
> to see a stack trace of where it happened.  That alone may be enough to
> help pinpoint the problem.
> 
> You may not actually get a core file generated.  "ulimit -a" will show
> whether core dumps will happen.  By default mine are set to 0, which is
> for no core dump.  Setting "ulimit -c unlimited", will allow the core
> file to be generated.  I'd suggest running gtkpod from a terminal, so
> you might find the core file.  Then gdb the core file.

What James says is right in principle. A backtrace certainly always helps.

Luckily, ipod_parse_artwork_db() is only called at one position in the 
code. The corresponding bug was fixed about 2 months 1 week ago in 
libgpod. Try upgrading to the the SVN version of libgpod.

Unfortunately, this segfault indicates that the iTunesDB could not be 
parsed successfully :-(

JCS.