Colin Fletcher wrote:
> Chris Cannam wrote:
> 
>> Can you run under valgrind and see what it says?
> 

[ Replying to myself. Snipped most of the valgrind output ]

> ==7746==  Address 0x5e75880 is 0 bytes inside a block of size 40 free'd
> ==7746==    at 0x40222EC: operator delete(void*) (vg_replace_malloc.c:342)
> ==7746==    by 0x8299426: 
> Rosegarden::RosegardenMainViewWidget::~RosegardenMainViewWidget() 
> (RosegardenMainViewWidget.cpp:235)
> ==7746==    by 0x482AF02: QMainWindow::setCentralWidget(QWidget*) (in 
> /usr/lib/libQtGui.so.4.4.0)
> ==7746==    by 0x82E6C55: Rosegarden::RosegardenMainWindow::initView() 
> (RosegardenMainWindow.cpp:910)

So, I naively tried commenting-out line 910 of RosegardenMainWindow.cpp, 
which incidentally, has a comment before it saying "//@@@ This was 
commented out... why?", and rosegarden no longer crashes when loading 
the example files.

However, this was (at best) a partial success, since then the main 
composition view is about 1 pixel high by 10 pixels wide, and immovably 
sat on top of the menu bar. Thus I conclude that the un-commenting of 
line 910 was done for a reason.

Hmm. Any more ideas? Is it just that I still have Qt 4.4? I see that 
since r10537, Qt 4.5 is needed to even compile trunk:

src/gui/widgets/FileDialog.cpp: In static member function ‘static 
QString Rosegarden::FileDialog::getOpenFileName(QWidget*, const 
QString&, const QString&, const QString&, QString*, 
QFlags<QFileDialog::Option>)’:
src/gui/widgets/FileDialog.cpp:74: error: ‘class Rosegarden::FileDialog’ 
has no member named ‘setOptions’

I'm reluctant to upgrade my Ubuntu 8.04 LTS to anything newer, but maybe 
it's a price I'll have to pay to keep up with the bleeding edge. Are you 
intending to support Qt 4.4?

Colin.

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Reply via email to