GNOME Bugzilla – Bug 149292
memprof crash on save
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: memprof Severity: major Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: memprof crash on save Bugzilla-Product: memprof Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Debugging custom server app. Can run leak checker, gets results. Also outputs some warnings: memintercept (25140): _MEMPROF_SOCKET = /tmp/memprof.58s0gG memintercept (25140): New process, operation = NEW, old_pid = 0 memprof: /usr/lib/libstdc++.so.5.0.5: No symbols memprof: Bad address memprof: /lib/libgcc_s-3.3.3-20040413.so.1: No symbols memprof: /usr/lib/libmemintercept.so: No symbols ** (memprof:25137): WARNING **: Cannot read word 0/16 in block 0xe79e98: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/2 in block 0xe79e90: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/115 in block 0xf1a300: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/178 in block 0xf1a020: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/2787 in block 0x104e060: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/1026 in block 0x104d040: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/16 in block 0x1192060: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/11 in block 0x1192030: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/8 in block 0x11bd05c: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/2 in block 0x11bd054: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/5208 in block 0xbe27a80: Input/output error ** (memprof:25137): WARNING **: Cannot read word 0/2983 in block 0xbe24be0: Input/output error Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? This happens reliably (for this application). I've used memprof successfully on other apps. Additional Information: No, I'm not keeping this data/version of program around to regenerate bug. But if needed, I can do so in the future. Debugging Information: Backtrace was generated from '/usr/bin/memprof' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (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)...[Thread debugging using libthread_db enabled] [New Thread -150187904 (LWP 25137)] (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)...0x006de402 in ?? ()
+ Trace 49099
Thread 1 (Thread -150187904 (LWP 25137))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-04 11:21 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "memprof". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was brian@cse.lehigh.edu. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** This bug has been marked as a duplicate of 97756 ***