GNOME Bugzilla – Bug 610272
crash in Terminal: ssh to a chinese bbs
Last modified: 2010-02-23 21:38:28 UTC
Version: 2.28.2 What were you doing when the application crashed? ssh to a chinese bbs Distribution: Unknown Gnome Release: 2.28.2 2010-02-17 (FreeBSD GNOME Project) BugBuddy Version: 2.28.0 System: FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #12 r203980M: Wed Feb 17 10:30:32 UTC 2010 root@fb.localdomain:/usr/obj/usr/src/sys/MYK amd64 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad Memory status: size: 172089344 vsize: 172089344 resident: 34283520 share: 70237674 rss: 34283520 rss_rlim: 8370 CPU usage: start_time: 0 rtime: 2944 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 128 Backtrace was generated from '/usr/local/bin/gnome-terminal' [New Thread 8050094c0 (LWP 100227)] [New Thread 8050071c0 (LWP 100282)]
+ Trace 220611
Thread 34443662528 (LWP 100227)
Thread 1 (Thread 8050094c0 (LWP 100227))
----------- .xsession-errors --------------------- WARNING: recurring into frame construction: 'mPresContext->mLayoutPhaseCount[eLayoutPhase_FrameC] == 0', file ./nsPresContext.h, line 1026 WARNING: recurring into frame construction: 'mPresContext->mLayoutPhaseCount[eLayoutPhase_FrameC] == 0', file ./nsPresContext.h, line 1026 ++DOMWINDOW == 30 (0x80d93b058) [serial = 116] [outer = 0x80dc1cc00] ++DOMWINDOW == 31 (0x8098de058) [serial = 117] [outer = 0x80dc1b800] ++WEBSHELL 0x80fd6dc00 == 14 ++DOMWINDOW == 32 (0x80fd6e458) [serial = 118] [outer = 0x0] ++DOMWINDOW == 33 (0x80fd6f458) [serial = 119] [outer = 0x80fd6e400] --DOMWINDOW == 32 (0x80aae8858) [serial = 111] [outer = 0x80d87cc00] [url = about:blank] --DOMWINDOW == 31 (0x80d906c58) [serial = 108] [outer = 0x80d8ff400] [url = http://www.google.com/search?hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aunofficial&hs=4W7&newwindow=1&q=freebsd+ext4&b --DOMWINDOW == 30 (0x80aae7458) [serial = 105] [outer = 0x80d8ff400] [url = http://www.google.com/search?q=freebsd+ext3&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a] Error accessing memory address 0x7fffffbff000: Bad address. Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Created attachment 154106 [details] the backtrace from gdb66 sorry,I'm using FreeBSD,there is no special debug symbols package. I think this is a bug of pango
If you can reproduce, please do a pmap (or cat /proc/PID/maps) on the process and grep for fonts. See which fonts it's using, and let me know. Thanks
Never mind. I think I found the root of the problem in the other bug. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 604128 ***