Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 12 of 12
hmm...it's seems I can't easily catch function that leaves its memory unfreed...) There is no single one...) Oh, I think it would be a long travel...) Thinking about a trick, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux Newbie
    Join Date
    Apr 2010
    Location
    Novosibirsk, Russia
    Posts
    145

    hmm...it's seems I can't easily catch function that leaves its memory unfreed...) There is no single one...) Oh, I think it would be a long travel...) Thinking about a trick, writing gdb script...That's very interesting time I mean, when I still working on this problem...) Can I get info about allocated memory regions in any wat by gdb command?...

  2. #12
    Linux Newbie
    Join Date
    Apr 2010
    Location
    Novosibirsk, Russia
    Posts
    145
    Quote Originally Posted by Schmidt View Post
    hmm...it's seems I can't easily catch function that leaves its memory unfreed...) There is no single one...) Oh, I think it would be a long travel...) Thinking about a trick, writing gdb script...That's very interesting time I mean, when I still working on this problem...) Can I get info about allocated memory regions in any wat by gdb command?...
    I found it can be done with 'cat /proc/$PID/maps'. I think I'll try to use GDB source command and execute a script that catches changes in memory maps, which would stop if some function will do "bad things". Then I suppose I should find all of bad functions.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •