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 476534 - crash in Anjuta IDE: I was just compiling a p...
crash in Anjuta IDE: I was just compiling a p...
Status: RESOLVED DUPLICATE of bug 467698
Product: anjuta
Classification: Applications
Component: plugins: message-view
2.2.0
Other All
: High critical
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-13 12:30 UTC by Marcio H Zuchini
Modified: 2007-09-15 18:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Marcio H Zuchini 2007-09-13 12:30:40 UTC 
What were you doing when the application crashed?
I was just compiling a program (C++) which I know was OK. I was testing Anjuta on a Turion 64 1.5 GB RAM, Sabayon Linux box. The test program was already been compiled succesfully by 'make' and gcc


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.1 2007-05-04 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-sabayon #1 SMP Wed Aug 1 22:48:31 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Human-Graphite
Icon Theme: Tango

Memory status: size: 303951872 vsize: 303951872 resident: 29310976 share: 18644992 rss: 29310976 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189675524 rtime: 211 utime: 191 stime: 20 cutime:35 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/anjuta'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
0x00002b579ecffad5 in waitpid () from /lib/libpthread.so.0

+ Trace 162603

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /usr/lib/libanjuta.so.0
  • #4 ??
    from /usr/lib/libanjuta.so.0
  • #5 ??
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 main 






Comment 1


Johannes Schmid





          2007-09-13 15:17:39 UTC
        



The backtrace is not very informative, but it seems to be a duplicate of of bug #467698! If you can comfirm that the behaviour is the same, please mark as duplicate or provide a better stacktrace:

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!







Comment 2


Johannes Schmid





          2007-09-15 18:23:55 UTC
        




*** This bug has been marked as a duplicate of 467698 ***