User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8a3) Gecko/20040829 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8a3) Gecko/20040829 If I try to run Mozilla under control of gdb, then I get Program terminated with signal SIGTRAP, Trace/breakpoint trap. The program no longer exists. (gdb) Reproducible: Always Steps to Reproduce: 1.build the current Mozilla snapshot using "configure --prefix=/usr/local/stow/mozilla-1.8 --enable-default-toolkit=gtk2 --enable-crypto --enable-debug" 2.run "mozilla -g" and enter "run" at GDB's prompt Platform: Debian for amd64, based upon gcc-3.4.1. Seems that gdb 6.1 and 6.2 can't debug pthread applications on amd64 at all. But the current snapshot for GDB is much better. Actually, this might be a problem of GDB, but Google shows that the error message "Program terminated with signal SIGTRAP" came up before, and it was always related with Mozilla or Firefox. This problem seriously affects debugging, so I would suggest to increase its priority.
PS: I could attach gdb to a running Mozilla, so I guess its not _that_ important anymore.
"current Mozilla snapshot", does that mean you used the Debian source for building Mozilla? If yes, please use http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest/mozilla-source.tar.bz2 or http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest/mozilla-source.tar.gz to build Mozilla (the Debian People modified Mozilla source).
No, I have not used the Debian version. Latest snapshot means http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/mozilla-source.tar.bz2 Please check the provided Build Identifier. I know that the Mozilla folks don't care very much about amd64, even though it is getting more and more important. Can you reproduce the problem?
I don't have an amd64 machine to reproduce, though shaver might. My suspicion is that this is a gdb bug, since I can't find any instances in the Mozilla code proper to SIGTRAP. It's conceivable that one of the libraries (eg GTK) is causing it, I suppose.
I do at least half of my development on an amd64 (fedora core 3) system with FC3-stock gdb and gcc and kernel, and I haven't had that problem.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.