On 11/2/06, Ken Moffat <[EMAIL PROTECTED]> wrote:
On Thu, Nov 02, 2006 at 07:09:14AM -0800, Dan Nicholson wrote: > > > >The other thing you can do is run "firefox -g" and it will run it > >through a debugger. I think it will automatically pick gdb as the > >default, but you might have to add "-d gdb". After that, you're trying > >to decipher a backtrace, so good luck with that. > Sorry, I forget that not everyone is on all of the lists where I randomly scatter my thoughts (e.g. clfs-support). Yes, I've been running it with -g (had to upgrade to gdb-6.5 to get a bt), that's how I knew it was early in main - unfortunately, "single stepping" seemed to run a bit more than I expected, but I've always found gdb to be hard to master.
Care to share the bt? Not that I'm a programmer, but I'd like to see it.
I've spent so long fiddling with run-mozilla.sh that I'd erased it from my memory by the time I came back to firefox. Thanks. In the meantime, I'm patching it with fprintf(stderr, "at point 1\n"); to try to see exactly where it fails. There's still a reasonable chance the problem is either specific to how I've tried to handle the multilib gtk2 and pango files, or else something specific to building on ppc64.
You could try strace to see if it's opening the right libraries/files/etc. strace -f -e trace=file -o log firefox And of course, ppc64 needs the pragma_visibility hack, but I think you already knew that. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
