Apologies if this is in the wrong place but it's not really a bug,
probably me doing something daft...

I've been using Songbird for a while now (great work) but recently
it's started crashing on me - I can start it and do nothing for 5
minutes and it still fails. I'm a Software Engineer by trade
(currently C++ on Windows CE) so I thought I'd try to track it down
myself. My best guess right now is that I just imported 40 GB of music
from my old iPod, so either the quantity is problematic or some of the
files are oddly formatted or corrupted.

I've checked out all the source and dependencies and installed all the
tools. I only have Visual Studio 2008 SP1 at home so I've disabled the
compiler warning for MSVC9. But when I try to build it seems to be
looking for a directory sbird\dependencies\vendor\mozbrowser. My
checkout doesn't have this directory, but it does have sbird
\dependencies\vendor\mozilla\browser. Has the layout of the dependecy
directory changed recently and the build not changed with it? Or have
I missed something? I can see some code in sbird\songbird.mk to get
mozbrowser from SVN but there's nothing in SVN at this location.

Once I've got this sorted I assume I can run the debug version of
Songbird, but what's the best way of getting debugging and getting
more information about the crash? There's a script somewhere to
create .vcproj files but it says this can't be used for building, just
viewing the code in Visual Studio.

Thanks for your advice,

Tom

Hey Tom,

On Nov 1, 3:49 pm, parsleythelion <parsle...@gmail.com> wrote:

Just a heads up that that VC9 check exists for a reason, and VC9 is
not supported; I do believe Songbird builds with VC9, but since we
have binary dependencies that are used in the build (and compiled with
VC8), you may experience crashes with VC9 that others won't see, and
bug reports against VC9 typically get triaged as"try a build with VC8
and let us know what happens." Just FYI... :-)

It should be available; there are currently a couple of problems with
SVN right now that we're working on fixing; to work around this, try:

cd dependencies\vendor
rm -rf mozbrowser
svn co http://publicsvn.songbirdnest.com/vendor/trunk/mozbrowser

That should at least get you building.

You'll probably want to build in debug mode; make -f songbird.mk debug
is a good place to start, and will spew a fair amount of debug goo on
the console.

good luck,
preed

Build is working now. I also had to rename dependencies\windows-i686-msvc8
to dependencies\windows-i686.

I think the reason mozbrowser wasn't checked out is that mozilla-build 1.3
includes SVN 1.4.2. When I ran the build yesterday I noticed "svn: This
client is too old to work with working copy 'sbird\trunk'; please get a
newer Subversion client". I guess the SVN server is 1.5.x.

When I run my build I get a series of assertions:
ASSERTION: Default pref file not parsed successfully.: 'Error', file
e:/builds/xulrunner/xr_trunk_reagan/mozilla/modules/libpref/src/nsPrefServi ce.cpp,
line 723
ASSERTION: Wrong thread: 'NS_IsMainThread()', file
e:/builds/xulrunner/xr_trunk_reagan/mozilla/netwerk/base/src/nsIOService.cp p,
line 477
ASSERTION: Using observer service off the main thread!: 'Error', file
e:/builds/xulrunner/xr_trunk_reagan/mozilla/xpcom/ds/nsObserverService.cpp,
line 130

These second two then repeat for longer than it takes for me to get bored of
pressing Ignore. Are these errors caused by MSVC9? Do you use the free
version of Visual Studio 2005 Express or one of the paid ones?

Tom

2008/11/3 preed <jpr...@gmail.com>

On Nov 3, 12:27 am, "Tom Isaacson" <parsle...@gmail.com> wrote:

Yeah, that's a the platform detection going wonky because of VC9.

publicsvn.s.c is SVN 1.4.6; I just noticed you get this message if you
used a 1.5.x client to perform a checkout (or TortoiseSVN), and then
try to do a build; it will use the SVN client with Mozilla build, and
fail when trying to run "svn info"; if you check out using the svn in
MozillaBuild, it should be fine.

The Win32 reference compilers we use are MSVC8, from Visual Studio; we
don't use the Express editions.

You do get a lot of assertions on startup; you might try setting
XPCOM_DEBUG_BREAK=warn in your environment; see
https://developer.mozilla.org/en/Debugging_Mozilla_on_Windows_FAQ#Dis...
for more information.

-Preed

export XPCOM_DEBUG_BREAK=warn is your friend here.

See Environment
Variables<http://wiki.songbirdnest.com/Docs/Environment_Variables>on
our wiki for other fun ones

David