Hi, On Mon, Apr 23, 2007 at 03:29:21AM +0000, brian m. carlson wrote: > picard crashes (with a SIGSEGV) unpredictably whilst tagging. However, > it seems that it can be triggered (I haven't checked that this is > completely correlated, but it does seem to be the pattern) by dropping a > large number of files onto the "New files (drag files to tag here)" > folder, and then after Picard has autotagged some (and is still looking > up others), open some of the new albums that have been autotagged and > save the tags. Sometimes, it will segfault. > > Note, however, that it seems to crash more often on some files than > others. I am willing to provide a file (4.5M) that seems to cause > crashes, but I cannot post it to the bug due to copyright concerns.
If its commercial music, you probably can't send it to anyone privately either... > I have, however, provided a backtrace from a crash under GDB. The file > containing the backtrace is attached. I have filed the bug here because > picard crashes in a file that belongs to this package; since picard is > written in python, it shouldn't be able to segfault on its own. > > Also note that if the crashes are related to the files, and if the > SIGSEGV can be used in arbitrary code execution, then this is a grave > bug which should be tagged "security". That's a pretty big leap from what we know so far, and at worst it is local(remote) for the user running things they picked up on the street (or maybe from the l337 'kitters at s*ny ;) Until we know what it is about the data (if anything) that triggers this, its just another bug to fix. All segfaults are bad. > If you need more information, please feel free to let me know. Actually attaching the backtrace is probably a pretty good start ;-) I'm not sure what is likely to be done about this yet... We have wx 2.8 on the horizon, which should probably replace 2.6 sometime very soon, but then we also have wx 2.9 looming, which sounds like it is going to break the string handling on all existing apps again, so I'm not sure who is going to want to move where when... But in the meantime, getting some idea of where and why this prangs is probably not a terrible idea. Have you browsed the volumes of the wx bug tracker to see if anyone else has reported something similar? Cheers, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
