From: SourceForge.net <no...@so...> - 2006-12-21 18:08:14
|
Bugs item #1620339, was opened at 2006-12-21 18:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109655&aid=1620339&group_id=9655 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: xine-lib Group: v1.1.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Matthias Drochner (drochner) Assigned to: Nobody/Anonymous (nobody) Summary: video_out_xv can free() wrong pointers Initial Comment: If a system runs out of shared memory while a xine application is running, the "use_shm" flag is set to 0. From that point, free() is used to free image buffers, regardless whether the buffer was allocated in shared memory before. On my box (NetBSD), this leads to diagnostic output from libc ("junk pointer, too high to make sense"). The appended patch changes the "dispose" function to check the "shmaddr" field of "shminfo" which should tell whether the individual buffer was allocated in shared memory or not. With that in place, I don't get the libc warnings anymore. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109655&aid=1620339&group_id=9655 |
From: SourceForge.net <no...@so...> - 2006-12-25 15:20:07
|
Bugs item #1620339, was opened at 2006-12-21 19:08 Message generated for change (Comment added) made by dgp85 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109655&aid=1620339&group_id=9655 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: xine-lib Group: v1.1.3 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Matthias Drochner (drochner) >Assigned to: Diego Pettenò (dgp85) Summary: video_out_xv can free() wrong pointers Initial Comment: If a system runs out of shared memory while a xine application is running, the "use_shm" flag is set to 0. From that point, free() is used to free image buffers, regardless whether the buffer was allocated in shared memory before. On my box (NetBSD), this leads to diagnostic output from libc ("junk pointer, too high to make sense"). The appended patch changes the "dispose" function to check the "shmaddr" field of "shminfo" which should tell whether the individual buffer was allocated in shared memory or not. With that in place, I don't get the libc warnings anymore. ---------------------------------------------------------------------- Comment By: Diego Pettenò (dgp85) Date: 2006-12-25 16:20 Message: Logged In: YES user_id=60011 Originator: NO This bug entry is believed to be fixed in CVS. Please reopen it if needed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109655&aid=1620339&group_id=9655 |