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 490586 - picking the wrong program to generate a useless stacktrace
picking the wrong program to generate a useless stacktrace
Status: RESOLVED DUPLICATE of bug 172394
Product: bug-buddy
Classification: Deprecated
Component: general
2.20.x
Other All
: Normal enhancement
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-26 16:59 UTC by Hans Breuer
Modified: 2008-10-02 14:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Hans Breuer 2007-10-26 16:59:24 UTC 
Version: @0.96.1@

What were you doing when the application crashed?
trying to reproduce bug #490546 ;) You have to choose a less robust import filter, DXF worked to crash


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.20.1 2007-10-23 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-gentoo-r8 #1 SMP Sun Sep 30 14:36:27 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 308404224 vsize: 308404224 resident: 159854592 share: 14196736 rss: 159854592 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193417819 rtime: 11738 utime: 11600 stime: 138 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
0x0000000038056849 in _start () from /lib64/ld-linux-x86-64.so.2

+ Trace 173084

  • #0 _start
    from /lib64/ld-linux-x86-64.so.2
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ?? 






Comment 1


Hans Breuer





          2007-10-27 11:54:14 UTC
        



I was running a debug version of Dia from /opt/bin/dia but bug-buddy picked up the installed version from /usr/bin/dia to generate the useless stack-trace above. 
Would it be possible to check for the process origin before creating a stacktrace of the wrong thing. Or maybe detect the broken stack trace and not put it into bugzilla?






Comment 2


Cosimo Cecchi





          2008-10-02 14:15:35 UTC
        



I believe this was a dup of bug 172394, which is fixed now in trunk.



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