[8098] in athena10

home help back first fref pref prev next nref lref last post

Re: [Debathena] #84: xdsc crashes on adding a meeting

daemon@ATHENA.MIT.EDU (Debathena Trac)
Tue Aug 2 09:33:23 2011

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: andersk@mit.edu, geofft@mit.edu, broder@mit.edu, jdreed@mit.edu
Date: Tue, 02 Aug 2011 13:33:15 -0000
Reply-To: 
Message-ID: <053.61bc6b7aeb79e6088e445b67ecc0a452@mit.edu>
In-Reply-To: <044.e55867ce899433452a37c9c576a5e5c1@mit.edu>
Content-Transfer-Encoding: 8bit

#84: xdsc crashes on adding a meeting---------------------+------------------------------------------------------
 Reporter:  andersk  |        Owner:                    
     Type:  defect   |       Status:  reopened          
 Priority:  trivial  |    Milestone:  The Distant Future
Component:  --       |   Resolution:                    
 Keywords:           |     See_also:                    
---------------------+------------------------------------------------------
Comment(by jdreed):
 So, I went and ran valgrind on xdsc, and based on my (possibly naive)
 interpretation of the output, it looks like Geoff's patch was right?

 {{{
 ==21275== Invalid free() / delete / delete[]
 ==21275==    at 0x4C282ED: free (vg_replace_malloc.c:366)

 [snip]
 ==21275==  Address 0x701e750 is 0 bytes inside a block of size 17 free'd
 ==21275==    at 0x4C282ED: free (vg_replace_malloc.c:366)
 ==21275==    by 0x4043E4: myfree (xdsc.c:1225)
 ==21275==    by 0x4071AD: AddCB (reply.c:715)
 }}}

 Memory management in C is definitely not my thing, though.  Unless there's
 any real interest in fixing this, I'm just going to go write a pygtk
 version.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/84#comment:7>Debathena <http://debathena.mit.edu/>MIT Debathena Project

home help back first fref pref prev next nref lref last post