[haiku-bugs] Re: [Haiku] #9945: BMediaFile leaks ca. 100 KB
- From: "anevilyak" <trac@xxxxxxxxxxxx>
- Date: Wed, 04 Sep 2013 21:08:42 -0000
#9945: BMediaFile leaks ca. 100 KB
------------------------------------+----------------------------
Reporter: ttcoder | Owner: nobody
Type: bug | Status: new
Priority: high | Milestone: R1
Component: Audio & Video/Codecs | Version: R1/Development
Resolution: | Keywords: ffmpeg
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
------------------------------------+----------------------------
Comment (by anevilyak):
Replying to [comment:4 ttcoder]:
> I wonder if there is a way I could set a "watchpoint" in Debugger on a
given heap area (rather than watch a given variable).. If yes then,
knowing in advance one of the addresses of leaked memory blocks (from a
previous run with printf() debug output ..etc) I could invoke debugger()
at the beginning of main(), set the watchpoint on that address, click
"Run" and get immediately notified (with an explicit backtrace) when that
memory block gets malloc()ed. If I know who malloc()s it I'll have a good
lead on who should be free()ing it yet fails to, probably.
You can set such a watchpoint ; when you right click -> watch, the
resulting dialog just prepopulates the address of the variable, but you're
free to change that to an arbitrary address. However, that won't do you
any good here, Haiku uses address space layout randomization, so the
addresses will not in any way be predictable between runs.
--
Ticket URL: <http://dev.haiku-os.org/ticket/9945#comment:5>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
