Nicolas Maître <nmai...@skynet.be> wrote: Hi,
>> Could you reproduce the crash and provide a gdb backtrace? We need to >> find out what crashes and where. > > I'd like, really. Maybe I'm too stupid but it seems I can't because of > deugging symbols missing: > Unknown daap tag: Aborting > [Thread 0x7ffff637e710 (LWP 6764) exited] Ah, f*ck it. It's not crashing, it's aborting due to the message being a fatal error and the log function just aborts in this case. So yeah, gdb will be useless here because it's actually working as designed when such an error is encountered. > Couldn't you reproduce the crash ? There's a non-nil chance that the problem is tied to the content of your library and I've dismantled my mt-daapd test setup a few weeks ago. I'll try to look into it if I can find some time :/ > PS: i've tried your forked-daapd package, and it works great ! It's > missing some "technical" doc, though ;) The idea is that it should just work with the appropriate config :) JB. -- Julien BLACHE - Debian & GNU/Linux Developer - <jbla...@debian.org> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
