blob: 1c59dd7c7fa807e99866a4b1580cc19418122978 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
[[!meta copyright="Copyright © 2010, 2016 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!tag open_issue_gnumach]]
IRC, unknown channel, unknown date.
<youpi> we really need something that is able to automatically check port deallocation
<youpi> at least for the trivial cases, for which we do have bugs I'm currently fixing...
<pochu> test suite? :)
<pochu> won't magically find them though, so not what you've asked for...
<youpi> test suites can trigger some of the bugs yes
<youpi> which is already a good thing
<youpi> of course the coverage can't be perfect
<youpi> one of the bugs I fixed happened only for setuid binaries for instance
- - -
portseal can automatically detect port leaks. It is somewhat
intrusive, as it leverages a source-transformation and hence requires
a recompilation of the code that contains the port leak. Currently,
it is a prototype. If you are looking for a port leak, I'd love you
to try it though:
[[http://darnassus.sceen.net/cgit/teythoon/portseal.git]]
|
