From: Dave P. <dp...@we...> - 2009-10-31 08:56:04
Attachments:
bug-549855_m100.rg
rosegardensegfault.txt
|
Hi, I filed bug 2885468 a while back and it was requested that I contact the list as well. When loading the attached file "bug-549855_m100.rg" I get a segfault. A copy of the gdb output and backtrace is attached. It still occurs in svn 11150. I've tried to debug it and if I step through AlsaDriver::connectSomething I don't get it I have to run full speed to 1308 setPlausibleConnection(toConnect->getId(), ""); for it to occur. Sorry my c and c++ skills are still in the making and I can't offer anymore help. Regards Dave P |
From: D. M. M. <mic...@ro...> - 2009-10-31 14:21:29
|
On Saturday 31 October 2009, Dave Plater wrote: > When loading the attached file "bug-549855_m100.rg" I get a segfault. I can confirm the crash. Thanks for the file. I'll investigate and see if I can do anything with it. If not, it'll have to wait for Chris to get back. This is his territory. -- D. Michael McIntyre |
From: D. M. M. <mic...@ro...> - 2009-10-31 14:44:17
|
On Saturday 31 October 2009, Dave Plater wrote: > When loading the attached file "bug-549855_m100.rg" I get a segfault. How did you create this file? The crash here is from the data being corrupt. The studio section has no devices at all. We should try to handle encountering this situation more gracefully than just crashing, but I'm a lot more concerned by the corruption itself than crashing upon encountering a completely indecipherable puzzle. From 0 to 0 which one of these do we choose when there should never be fewer than 1? Can you wind up in this situation reliably and get this crash to happen with a variety of other files? -- D. Michael McIntyre |
From: Dave P. <dp...@we...> - 2009-10-31 15:21:34
|
On 10/31/2009 04:44 PM, D. Michael McIntyre wrote: > On Saturday 31 October 2009, Dave Plater wrote: > > >> When loading the attached file "bug-549855_m100.rg" I get a segfault. >> > How did you create this file? The crash here is from the data being corrupt. > The studio section has no devices at all. > > We should try to handle encountering this situation more gracefully than just > crashing, but I'm a lot more concerned by the corruption itself than crashing > upon encountering a completely indecipherable puzzle. From 0 to 0 which one > of these do we choose when there should never be fewer than 1? > > Can you wind up in this situation reliably and get this crash to happen with a > variety of other files? > The file came from a bug report by an opensuse user that is trying out the thorn version. I'll find out more and report back. Thanks Dave P |
From: Dave P. <dp...@we...> - 2009-10-31 15:32:35
|
On 10/31/2009 05:19 PM, Dave Plater wrote: > On 10/31/2009 04:44 PM, D. Michael McIntyre wrote: > >> On Saturday 31 October 2009, Dave Plater wrote: >> >> >> >>> When loading the attached file "bug-549855_m100.rg" I get a segfault. >>> >>> >> How did you create this file? The crash here is from the data being corrupt. >> The studio section has no devices at all. >> >> We should try to handle encountering this situation more gracefully than just >> crashing, but I'm a lot more concerned by the corruption itself than crashing >> upon encountering a completely indecipherable puzzle. From 0 to 0 which one >> of these do we choose when there should never be fewer than 1? >> >> Can you wind up in this situation reliably and get this crash to happen with a >> variety of other files? >> >> > The file came from a bug report by an opensuse user that is trying out > the thorn version. I'll find out more and report back. > Thanks > Dave P > > Going back to the novell bugzilla bug : https://bugzilla.novell.com/show_bug.cgi?id=549855 The reporter said "it has been created with rosegarden4-1.7.3-0.pm.1from packman opensuse 11.1 x86_64 repository" I've asked him to check if the file hasn't been corrupted. Regards Dave P |
From: Julie S <msj...@ya...> - 2009-10-31 16:01:42
|
Dear RG Team, considering the issue stated: > puzzle. From 0 to 0 which one > > of these do we choose when there should never be fewer > than 1? A crash is bad, even if the file is corrupt. Sounds like a robustness issue. I guess we need to make certain we are not assuming the file is good...We should not trust it. That would require a pessimistic approach to file reading. We all know that the .rg are just compressed XML files, so anybody can and sometimes does hack these files. We can either silently, overlook these corruptions and load what we can, or we can warn about them, or we can refuse to allow the load, but crashing is a bad option. Those are my thoughts. Sincerely, Julie --- On Sat, 10/31/09, Dave Plater <dp...@we...> wrote: > From: Dave Plater <dp...@we...> > Subject: Re: [Rosegarden-devel] Rosegarden thorn Segmentation fault in AlsaDriver.cpp:1308 > To: "D. Michael McIntyre" <mic...@ro...> > Cc: ros...@li... > Date: Saturday, October 31, 2009, 11:19 AM > On 10/31/2009 04:44 PM, D. Michael > McIntyre wrote: > > On Saturday 31 October 2009, Dave Plater wrote: > > > > > >> When loading the attached file > "bug-549855_m100.rg" I get a segfault. > >> > > How did you create this file? The crash here is > from the data being corrupt. > > The studio section has no devices at all. > > > > We should try to handle encountering this situation > more gracefully than just > > crashing, but I'm a lot more concerned by the > corruption itself than crashing > > upon encountering a completely indecipherable > puzzle. From 0 to 0 which one > > of these do we choose when there should never be fewer > than 1? > > > > Can you wind up in this situation reliably and get > this crash to happen with a > > variety of other files? > > > The file came from a bug report by an opensuse user that is > trying out > the thorn version. I'll find out more and report back. > Thanks > Dave P > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference > in SF, CA > is the only developer event you need to attend this year. > Jumpstart your > developing skills, take BlackBerry mobile applications to > market and stay > ahead of the curve. Join us from November 9 - 12, 2009. > Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... > - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel > |
From: D. M. M. <mic...@ro...> - 2009-11-01 02:50:31
|
On Saturday 31 October 2009, Julie S wrote: > A crash is bad, even if the file is corrupt. Sounds like a robustness > issue. No doubt. I'm not arguing "oh, the crash is no big deal." I'm just more worried about what's saving crap .rg files in the first place. It seems Rosegarden Classic is saving crap .rg files in the first place. I imagine this used to work because we had all that auto creation garbage that would fill in something for the empty studio at runtime. It does, in fact, open just fine with 1.7.2 (the only version of Classic close to hand.) > I guess we need to make certain we are not assuming the file is good...We > should not trust it. That would require a pessimistic approach to file > reading. We generally have one. The XML parsing code is full of "Warning, element blah found outside of blither section" and so on. This one isn't actually a file reading thing per se anyway, so much as a "we need to either avoid crashing when something that shouldn't be null is null, or we should supply something so it's never null" issue. -- D. Michael McIntyre |
From: Dave P. <dp...@we...> - 2009-10-31 19:38:05
|
On 10/31/2009 04:44 PM, D. Michael McIntyre wrote: > On Saturday 31 October 2009, Dave Plater wrote: > > >> When loading the attached file "bug-549855_m100.rg" I get a segfault. >> > How did you create this file? The crash here is from the data being corrupt. > The studio section has no devices at all. > > We should try to handle encountering this situation more gracefully than just > crashing, but I'm a lot more concerned by the corruption itself than crashing > upon encountering a completely indecipherable puzzle. From 0 to 0 which one > of these do we choose when there should never be fewer than 1? > > Can you wind up in this situation reliably and get this crash to happen with a > variety of other files? > Here's the reply from the reporter :- --- Comment #5 from michel munnix <m.m...@re...> 2009-10-31 12:59:27 MDT --- I checked I can still open the file with rosegarden4-1.7.3-0.pm.1 and it seems ok to me. Having gunziped it to examine it, I confirm the studio is empty. I've never really managed to setup the studio correctly. Nor to make my sound work with jack So I usually work in rosegarden, export to midi, use a software synth to generate a wav file and encode it to mp3 to hear it on an mp3 device. I have made some new experiments with jack and it seems to improve so I tried with an other file which has a studio. It crashes at another point, so I open a new bug. I also loaded it into rosegarden-1.7.3 with no problem. Regards Dave P |
From: Dave P. <dp...@we...> - 2009-11-02 12:03:07
Attachments:
bug-551669_magnificat7.rg
|
On 10/31/2009 09:35 PM, Dave Plater wrote: > On 10/31/2009 04:44 PM, D. Michael McIntyre wrote: > >> On Saturday 31 October 2009, Dave Plater wrote: >> >> >> >>> When loading the attached file "bug-549855_m100.rg" I get a segfault. >>> >>> >> How did you create this file? The crash here is from the data being corrupt. >> The studio section has no devices at all. >> >> We should try to handle encountering this situation more gracefully than just >> crashing, but I'm a lot more concerned by the corruption itself than crashing >> upon encountering a completely indecipherable puzzle. From 0 to 0 which one >> of these do we choose when there should never be fewer than 1? >> >> Can you wind up in this situation reliably and get this crash to happen with a >> variety of other files? >> >> > Here's the reply from the reporter :- > > --- Comment #5 from michel munnix <m.m...@re...> 2009-10-31 12:59:27 MDT --- > I checked I can still open the file with rosegarden4-1.7.3-0.pm.1 and it seems > ok to me. > Having gunziped it to examine it, I confirm the studio is empty. > I've never really managed to setup the studio correctly. > Nor to make my sound work with jack > So I usually work in rosegarden, export to midi, use a software synth to > generate a wav file and encode it to mp3 to hear it on an mp3 device. > I have made some new experiments with jack and it seems to improve > so I tried with an other file which has a studio. It crashes at another point, > so I open a new bug. > > I also loaded it into rosegarden-1.7.3 with no problem. > Regards > Dave P > > I forgot to attach the file with studio mentioned above, it causes a sigsegv :- Program received signal SIGSEGV, Segmentation fault. Rosegarden::CompositionModelImpl::slotInstrumentParametersChanged (this=0x1ad4360, id=2002) at src/gui/editors/segment/compositionview/CompositionModelImpl.cpp:488 488 const Segment* s = *i; (gdb) subgraph starting at rosegarden timed out (subgraph_wait_fd=13, status = 0, state = Triggered, pollret = 0 revents = 0x0) Regards Dave P |
From: Chris C. <ca...@al...> - 2009-11-02 09:43:26
|
On Sat, Oct 31, 2009 at 2:44 PM, D. Michael McIntyre <mic...@ro...> wrote: > On Saturday 31 October 2009, Dave Plater wrote: > >> When loading the attached file "bug-549855_m100.rg" I get a segfault. > > How did you create this file? The crash here is from the data being corrupt. > The studio section has no devices at all. That should be legitimate (as you describe it -- I haven't examined the file in question). Open the device manager, delete all the devices, save the document -- should work. This crash sounds like a straightforward mistake on my part. Chris |