Menu
▾
▴
jazzplusplus-devel
|
From: joakim v. <jo...@ve...> - 2004-03-30 22:53:11
|
Hello, I've added the "sequence length" command the same way I added the "midi delay" dialog. Again, I choose this esoteric command rather than something useful because I originally coded the command and remembered how it worked. Some notes: - xrced limits the ranges of a spin ctrl for instance. You can extend the range by editing the file in emacs. - The xrc resource locator isnt very forgiving. If you forget to load the xrc, or the dialog resource has the wrong name it will segfault. Cheers, /Joakim |
|
From: Matt K. <ra...@ch...> - 2004-03-31 01:15:15
|
All, I've checked in my memory bug fixes and the PortMidi Makefile fix. No changes to functionality, just memory friendliness. Matt |
|
From: Matt K. <ra...@ch...> - 2004-03-31 01:24:22
|
All, FYI, I just checked the wxGTK core dump bug status on sourceforge. The developer said that my patch wouldn't work in all cases, and that other people are seeing similar core dumps in other placesin wxGTK, caused by the same compiler bug. He said that GCC 3.3 is just no good and that it must be updated in order to make wxGTK work correctly. I think my patch would probably fix JAZZ and probably Audacity, most likely, though. I still think this is somewhat of a cop-out on their part. They could re-write the global stuff to be immune to initialization order problems. There's not that much of it from what I can see. But, I don't think I alone can make them budge. This kinda sucks, because it will place compiler requirements on JAZZ (and Audacity, and......). I hate it when an app requires a certain compiler version to compile. Ack. Pthphfffft. It tends to make people more hesitant to try an app. Matt |
|
From: Dave F. <dav...@co...> - 2004-03-31 01:56:37
|
On Wednesday 31 March 2004 04:20 am, Matt Kelly wrote: > This kinda sucks, because it will place compiler requirements on > JAZZ (and Audacity, and......). I hate it when an app requires a > certain compiler version to compile. Ack. Pthphfffft. It tends > to make people more hesitant to try an app. To be honest, I'll bet we can safely ignore it and it'll go away. ;) I'm thinking that if a later version of GCC is known to work fine with wxGTK, the distributions will be picking it up, of course. We just make sure that we've saved all data already before the segfault comes and be happy. :) If users find it an inconvenience, we can just tell them to upgrade their compiler, and make some excuses about how it's a specific version of GCC and the bug is in the compiler itself, or in wxGTK, there's some disagreement over it, and nothing we can do except to recommend a different compiler. But like I said (I think it was here), since I never lost any data from Audacity doing this, I'm not particularly worried about it there, so we just make sure we've saved everything before the core dump. ;) Dave > Matt > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel -- Visit my website! http://www.davefancella.com/?event=em Lockwood's Long Shot: The chances of getting eaten up by a lion on Main Street aren't one in a million, but once would be enough. |
|
From: Matt K. <ra...@ch...> - 2004-03-31 02:49:39
|
Dave Fancella wrote: > On Wednesday 31 March 2004 04:20 am, Matt Kelly wrote: > >>This kinda sucks, because it will place compiler requirements on >>JAZZ (and Audacity, and......). I hate it when an app requires a >>certain compiler version to compile. Ack. Pthphfffft. It tends >>to make people more hesitant to try an app. > > > To be honest, I'll bet we can safely ignore it and it'll go away. ;) I'm > thinking that if a later version of GCC is known to work fine with wxGTK, the > distributions will be picking it up, of course. We just make sure that we've > saved all data already before the segfault comes and be happy. :) If users > find it an inconvenience, we can just tell them to upgrade their compiler, > and make some excuses about how it's a specific version of GCC and the bug is > in the compiler itself, or in wxGTK, there's some disagreement over it, and > nothing we can do except to recommend a different compiler. I suppose. Still bugs me though. :) > > But like I said (I think it was here), since I never lost any data from > Audacity doing this, I'm not particularly worried about it there, so we just > make sure we've saved everything before the core dump. ;) You are correct... I too have never lost anything to the core dumps. It's mostly cosmetic. Matt |
|
From: Dave F. <dav...@co...> - 2004-03-31 06:21:19
|
On Wednesday 31 March 2004 05:46 am, Matt Kelly wrote: > > But like I said (I think it was here), since I never lost any data from > > Audacity doing this, I'm not particularly worried about it there, so we > > just make sure we've saved everything before the core dump. ;) > > You are correct... I too have never lost anything to the core dumps. > It's mostly cosmetic. Hmm, I set out to prove that this bug in Audacity had the same cause earlier tonight, and latest Audacity cvs doesn't segfault on exit any more. The plot thickens.... ;) Dave -- Visit my website! http://www.davefancella.com/?event=em Your nature demands love and your happiness depends on it. |
|
From: Matt K. <ra...@ch...> - 2004-03-31 18:01:45
|
> > On Wednesday 31 March 2004 05:46 am, Matt Kelly wrote: > > > But like I said (I think it was here), since I never lost any data from > > > Audacity doing this, I'm not particularly worried about it there, so we > > > just make sure we've saved everything before the core dump. ;) > > > > You are correct... I too have never lost anything to the core dumps. > > It's mostly cosmetic. > > Hmm, I set out to prove that this bug in Audacity had the same cause earlier > tonight, and latest Audacity cvs doesn't segfault on exit any more. The plot > thickens.... ;) I did prove that my existing Audacity does indeed core dump for the same reason. Didn't try the CVS. One thing, though, is that this problem is caused by an initialization/ construction ordering problem. Maybe the latest CVS Audacity code causes a change in this order, causing the bug to go away. Matt |
|
From: Patrick E. <pa...@pa...> - 2004-03-31 06:18:27
|
Ya, that sounds like a great candidate for a FAQ entry. Just need to
make sure that any binaries we create are compiled with a sane
compiler.
3.3.3 suffers from the segfault as well. I haven't tried it on 3.4
since I'm waiting for Debian to move it from experimental to
unstable.
Patrick
On Tuesday 30 March 2004 10:57, Dave Fancella wrote:
> On Wednesday 31 March 2004 04:20 am, Matt Kelly wrote:
> > This kinda sucks, because it will place compiler requirements on
> > JAZZ (and Audacity, and......). I hate it when an app requires a
> > certain compiler version to compile. Ack. Pthphfffft. It tends
> > to make people more hesitant to try an app.
>
> To be honest, I'll bet we can safely ignore it and it'll go away.
> ;) I'm thinking that if a later version of GCC is known to work
> fine with wxGTK, the distributions will be picking it up, of
> course. We just make sure that we've saved all data already before
> the segfault comes and be happy. :) If users find it an
> inconvenience, we can just tell them to upgrade their compiler, and
> make some excuses about how it's a specific version of GCC and the
> bug is in the compiler itself, or in wxGTK, there's some
> disagreement over it, and nothing we can do except to recommend a
> different compiler.
>
> But like I said (I think it was here), since I never lost any data
> from Audacity doing this, I'm not particularly worried about it
> there, so we just make sure we've saved everything before the core
> dump. ;)
>
> Dave
>
> > Matt
> >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux Tutorials
> > Free Linux tutorial presented by Daniel Robbins, President and
> > CEO of GenToo technologies. Learn everything from fundamentals to
> > system
> > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=c
> >lick _______________________________________________
> > jazzplusplus-devel mailing list
> > jaz...@li...
> > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel
|
|
From: joakim v. <jo...@ve...> - 2004-03-31 07:10:33
|
It appears I'm running 3.2.2, and it's there as well. /Joakim Patrick Earl wrote: >Ya, that sounds like a great candidate for a FAQ entry. Just need to >make sure that any binaries we create are compiled with a sane >compiler. > >3.3.3 suffers from the segfault as well. I haven't tried it on 3.4 >since I'm waiting for Debian to move it from experimental to >unstable. > > Patrick > >On Tuesday 30 March 2004 10:57, Dave Fancella wrote: > > >>On Wednesday 31 March 2004 04:20 am, Matt Kelly wrote: >> >> >>>This kinda sucks, because it will place compiler requirements on >>>JAZZ (and Audacity, and......). I hate it when an app requires a >>>certain compiler version to compile. Ack. Pthphfffft. It tends >>>to make people more hesitant to try an app. >>> >>> >>To be honest, I'll bet we can safely ignore it and it'll go away. >>;) I'm thinking that if a later version of GCC is known to work >>fine with wxGTK, the distributions will be picking it up, of >>course. We just make sure that we've saved all data already before >>the segfault comes and be happy. :) If users find it an >>inconvenience, we can just tell them to upgrade their compiler, and >>make some excuses about how it's a specific version of GCC and the >>bug is in the compiler itself, or in wxGTK, there's some >>disagreement over it, and nothing we can do except to recommend a >>different compiler. >> >>But like I said (I think it was here), since I never lost any data >>from Audacity doing this, I'm not particularly worried about it >>there, so we just make sure we've saved everything before the core >>dump. ;) >> >>Dave >> >> >> >>>Matt >>> >>> >>> >>> >>> >>>------------------------------------------------------- >>>This SF.Net email is sponsored by: IBM Linux Tutorials >>>Free Linux tutorial presented by Daniel Robbins, President and >>>CEO of GenToo technologies. Learn everything from fundamentals to >>>system >>>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=c >>>lick _______________________________________________ >>>jazzplusplus-devel mailing list >>>jaz...@li... >>>https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel >>> >>> > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >jazzplusplus-devel mailing list >jaz...@li... >https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel > > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X