Re: memory leak (definition?)



Christopher Benson-Manica wrote:
> Flash Gordon <spam@xxxxxxxxxxxxxxxxxx> wrote:
>
> > The correct solution is to understand the SW you are using and how to
> > use it correctly. It is IMHO far more likely to be a problem in your
> > code than the code you are calling.
>
> Depends on which 3rd party wrote the kernel module, really.
>

Also, it depends highly on the quality of the documentation
provided with the module. The correct solution in this particular
situation is to stop using their software, but that's out
of my hands. Since my code is doing exactly 2 things:
calling their function to allocate a data structure and then calling
their code to free it, and their documentation claims that these
2 functions work together, it is in fact highly unlikely that the
problem is in my code. My understanding of their software
is sufficient to recognize that it is crap and that proper use
constitutes placing it in the garbage can.

My original question, which I can phrase more succinctly thanks
to Gordon Burditt's response, is whether the exec family of functions
will
play nicely with kernel memory. That question was posted here
only as an ancillary to what I thought was an interesting toy
question regarding the definition of a memory leak which I
thought might be interesting to some of the people
reading comp.lang.c. If you feel that it is entirely off topic
than the correct response is to either make no response
or respond outside of the group. The C language is and
has always been closely tied to the Unix heritage, and IMO
questions regarding the behavior of low-level functions
such as the exec family are in fact relevant to the language and
to this newsgroup. I recognize that many people have tried
to divorce this group from anything beyond the language
proper, and that is in fact why I don't bother reading the group
very often anymore.

.



Relevant Pages

  • Re: Clearing objects in a VBProject
    ... Thanks for your perserverance - I am looking for the correct solution. ... I didn't look closely enough to your response to notice that you were using ... "Tom Ogilvy" wrote: ... >> process in TaskManager. ...
    (microsoft.public.excel.programming)
  • Re: RFC: Starting a stable kernel series off the 2.6 kernel
    ... no one is calling 2.6 "stable" anymore than they are ... > in 200 LoC as has been claimed so often, ... Because it's not the correct solution. ... because an in-kernel devfs is not the correct thing to do. ...
    (Linux-Kernel)
  • Re: The basics of Windows messages
    ... As mentioned in your response, if an application does not process ... and 1) to be the correct solution. ... add calls to ProcessMessages/DoEvents/PeekMessage loop inside your ...
    (microsoft.public.win32.programmer.kernel)
  • Re: The basics of Windows messages
    ... but I would like to add that most experienced developers consider 2) to ... and 1) to be the correct solution. ... The reason I focused my question on option 2) is that I wish to understand the execution flow from the point amid the lengthy process, where /ProcessMessages/ is called, to the queue processing, and then back to the calling site, where the lengthy process is resumed. ... William's response has already taken me much closer in that direction, but I think I might still need another round. ...
    (microsoft.public.win32.programmer.kernel)