I'm trying to help with getting a backtrace on the bug to which your helpful email below refers. I'd love to see this bug cleared!

I've followed http://wiki.debian.org/?HowToGetABacktrace
building and installing mozilla-calendar and its build-deps. Whew!

I'm no gdb expert.  The gnome menu command that launches mozilla-calendar is
  mozilla-suite -calendar
and
  /usr/bin/mozilla-suite
is a shell script that sets up the complex mozilla environment and (somehow) runs the relevant program.

Following your instructions,
$ MALLOC_CHECK_=2 gdb mozilla-suite
gives me the error:
...This GDB was configured as "x86_64-linux"..."/usr/bin/mozilla-suite": not in executable format: File format not recognized

(presumably because it's a shell script)

How do I get the required backtrace?

NB for your info:
- mozilla-calendar on my AMD64 segfaults immediately on startup
- I'm using up-to-date etch, and the mozilla-calendar version is 2:1.7.8-1sarge2 (so if I understand your question, this is NOT a regression - the bug is there in 2:1.7.8-1sarge2)

If you can get me over this hurdle to get a backtrace, I'll post it to you and the bug-report, and then offer to try again with the mozilla-calendar version in unstable (if I must - I don't want to drag too much in from unstable).

Thanks,
Barry

--------------

From [EMAIL PROTECTED] Mon Oct 17 05:39:26 2005
Date: Mon, 17 Oct 2005 14:39:00 +0200
From: Loic Minier <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: mozilla-calendar: crashes still

On jeu, ao=FB 04, 2005, Teemu Ikonen wrote:
> This package has been unusable for its purpose in certain
> architectures for over six months now (including the versions in
> unstable).

 Is this a regression over version 2:1.7.8-1sarge2 in testing?

 If yes, please provide a backtrace of the crash as explained at:
    <http://wiki.debian.org/?HowToGetABacktrace>

   Thanks,
--=20
Lo=EFc Minier <[EMAIL PROTECTED]>





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to