After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 424880 - crash in Text Editor: i have closed the sh scr...
crash in Text Editor: i have closed the sh scr...
Status: RESOLVED DUPLICATE of bug 346444
Product: gedit
Classification: Applications
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-31 14:40 UTC by bion
Modified: 2007-05-30 06:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description bion 2007-03-31 14:40:07 UTC
Version: 2.18.0

What were you doing when the application crashed?
i have closed the sh script.


Distribution: Unknown
Gnome Release: 2.18.0 2007-03-27 (FreeBSD GNOME Project)
BugBuddy Version: 2.18.0

System: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007     root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 34112 vsize: 34112 resident: 22484 share: 28448256 rss: 22484 rss_rlim: 5621
CPU usage: start_time: 0 rtime: 798 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133

Backtrace was generated from '/usr/local/bin/gedit'

(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100185]
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100185]
0x290f16cd in wait4 () from /lib/libc.so.6

Thread 1 (LWP 100185)

  • #0 wait4
    from /lib/libc.so.6
  • #1 waitpid
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.2
  • #3 libgnomeui_module_info_get
    from /usr/local/lib/libgnomeui-2.so.0
  • #4 sigaction
    from /lib/libpthread.so.2
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 sigaction
    from /lib/libpthread.so.2
  • #11 _fini
    from /usr/local/lib/libglade/2.0/libbonobo.so
  • #12 tls_dtv_generation
    from /libexec/ld-elf.so.1
  • #13 ??
    from /libexec/ld-elf.so.1
  • #14 ??
  • #15 elf_hash
    from /libexec/ld-elf.so.1
  • #16 elf_hash
    from /libexec/ld-elf.so.1
  • #17 __cxa_finalize
    from /lib/libc.so.6
  • #18 exit
    from /lib/libc.so.6
  • #19 _start
  • #20 ??
Output of custom script "/usr/local/lib/gedit-2/gedit-bugreport.sh":
Active plugins:

No plugin installed in $HOME.





----------- .xsession-errors (47942 sec old) ---------------------
amarok: BEGIN: virtual void ThreadManager::Thread::run()
amarok: BEGIN: virtual bool ScanController::doJob()
amarok: BEGIN: SqliteConnection::SqliteConnection(const SqliteConfig*)
amarok: END__: SqliteConnection::SqliteConnection(const SqliteConfig*) - Took 0.0021s
amarok: END__: virtual bool ScanController::doJob() - Took 0.0032s
amarok: END__: virtual void ThreadManager::Thread::run() - Took 0.0044s
amarok: [CollectionDB] JobFinishedEvent from Incremental ScanController received.
amarok: [ThreadManager] Job completed: CollectionScanner. Jobs pending: 0
amarok: BEGIN: virtual ScanController::~ScanController()
amarok: END__: virtual ScanController::~ScanController() - Took 0.00047s
amarok: [ThreadManager] Threads in pool: 3
amarok: BEGIN: ScanController::ScanController(CollectionDB*, bool, const QStringList&)
amarok: BEGIN: void ScanController::initIncremental()
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-05-02 11:42:44 UTC
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.
Thanks in advance!
Comment 2 Baptiste Mille-Mathias 2007-05-30 06:36:18 UTC
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 346444 ***