Firebug 1.5 on Fedora 11 64 Bit FF 3.5.4

[httpete]

I have stayed up with firebug 1.5, which worked fine for a while, and
then started causing my firefox to crash, it wont even start. Firebug
1.4.5 works just fine. I get a seg fault. Is this a known issue? I am
using the FF that ships with Fedora 11.

[John J Barton]

Try a 32bit Firefox from the Firefox download site. The issue is
known, but it is in jsd which has no owner currently.
jjb

[httpete]

I need firefox 64 bit. Can you tell me the bug so I can track it or
give more information? For developers who use firebug, 64 bit is our
primary dev env.

[John J Barton]

On Nov 9, 6:39 am, httpete <smitp...@yahoo.com> wrote:
> I need firefox 64 bit. Can you tell me the bug so I can track it or
> give more information?

https://bugzilla.mozilla.org/show_bug.cgi?id=513556

> For developers who use firebug, 64 bit is our
> primary dev env.

I'm not sure what you meant to say here, but the statement as it
stands is almost certainly incorrect.
jjb

[Marcus Better]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John J Barton wrote:
> https://bugzilla.mozilla.org/show_bug.cgi?id=513556

I get "You are not authorized to access bug #513556". Is it security-
related?

Cheers,

Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkr5NG0ACgkQXjXn6TzcAQljZgCeN5CgMZqG15OVqkLZw/XF8gf4
4CAAnjjcNulizwdbk8h1ayTq2Sg1fPhi
=o+d+
-----END PGP SIGNATURE-----

[Marcus Better]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

httpete wrote:
> I need firefox 64 bit. Can you tell me the bug so I can track it or
> give more information?

See also
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542768
https://bugs.launchpad.net/debian/+source/iceweasel/+bug/449744

Cheers,

Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkr5PdgACgkQXjXn6TzcAQk5rQCg5pfjQXqDhaJ7qKOwV+qufvF+
MecAoJgdnSrQfzMjQFzAER3DcV5WZakJ
=J1e3
-----END PGP SIGNATURE-----

[John J Barton]

On Nov 10, 1:37 am, Marcus Better <mar...@better.se> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> John J Barton wrote:
> >https://bugzilla.mozilla.org/show_bug.cgi?id=513556
>
> I get "You are not authorized to access bug #513556". Is it security-
> related?

No but it is classified as such I guess because so many crashes can be
used for exploits.

jjg

[httpete]

John, firebug has worked in 64 bit firefox for as long as I have used
it. I need it to work on firefox just as it has.

[John J Barton]

On Nov 16, 1:59 pm, httpete <smitp...@yahoo.com> wrote:
> John, firebug has worked in 64 bit firefox for as long as I have used
> it. I need it to work on firefox just as it has.

Ok, so how can I help you? All versions of Firebug are available from
http://getfirebug.com/releases. Just pick one that has worked for you
before.

jjb

[Marcus Better]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John J Barton wrote:
>> >https://bugzilla.mozilla.org/show_bug.cgi?id=513556
>>
>> I get "You are not authorized to access bug #513556". Is it security-
>> related?
>
> No but it is classified as such I guess because so many crashes can be
> used for exploits.

Do you know whom I should contact to possibly lift the restriction, or to
get access to the report? It will be easier to fix it if the bug report is
available.

Assuming you can view the report, do you think there is anything sensitive
in there that is not already in this public report anyway:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542768

Cheers,

Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAksDwoIACgkQXjXn6TzcAQkh3QCgqKQ1Jh8AZ3rMMaCdTrMjB/+5
TyUAniZ5bVmqGUCwp5S6OrHfn4BiBEAt
=irmV
-----END PGP SIGNATURE-----

[John J Barton]

On Nov 18, 1:46 am, Marcus Better <mar...@better.se> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> John J Barton wrote:
> >> >https://bugzilla.mozilla.org/show_bug.cgi?id=513556
>
> >> I get "You are not authorized to access bug #513556". Is it security-
> >> related?
>
> > No but it is classified as such I guess because so many crashes can be
> > used for exploits.
>
> Do you know whom I should contact to possibly lift the restriction, or to
> get access to the report? It will be easier to fix it if the bug report is
> available.
>
> Assuming you can view the report, do you think there is anything sensitive
> in there that is not already in this public report anyway:
>  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542768

The callstack on the debian.org looks like the call stack on the
mozilla site.

According to the mozilla bug report this crash does not happen on FF
3.7. So if you can get the nightly builds for FF 3.7 between the time
they branched from FF 3.6 and the time you first saw the crash.
(2009-08-30 for mozilla report), you can do a binary search and find
the day that FF 3.7 fixed the crash. That would go a long way to get
the fix for 3.6.

jjb

[John J Barton]

Turns out this is a duplicate of a bug that has been fixed:
https://bugzilla.mozilla.org/show_bug.cgi?id=513556

All that needs to happen is for the patch to land on FF 3.6.

jjb