summaryrefslogtreecommitdiff
path: root/open_issues
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2010-07-30 16:36:06 +0200
committerThomas Schwinge <thomas@schwinge.name>2010-07-30 16:36:06 +0200
commitf1287e2af0f8ab27c639c536a34090bc6b0d0a2b (patch)
tree3ccb48f4a8300d6412431210249f909a4bc33adc /open_issues
parentbf39e4e31e58242ab686c56bbf51678f272bbc15 (diff)
open_issues/libasyncns: New.
Diffstat (limited to 'open_issues')
-rw-r--r--open_issues/libasyncns.mdwn19
1 files changed, 19 insertions, 0 deletions
diff --git a/open_issues/libasyncns.mdwn b/open_issues/libasyncns.mdwn
new file mode 100644
index 00000000..bbd34bff
--- /dev/null
+++ b/open_issues/libasyncns.mdwn
@@ -0,0 +1,19 @@
+[[!meta copyright="Copyright © 2010 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_porting]]
+
+IRC, unknown channel, unknown date.
+
+ <pinotree> tschwinge: btw, would you be able to tell if and what's wrong with a socket-related problem?
+ <pinotree> it is reproducible with a very small self-contained C library
+ <pinotree> http://0pointer.de/lennart/projects/libasyncns/
+ <pinotree> it has a test case with it, which fails
+ <pinotree> tschwinge: if that can ring some bell, imho the problem is related to SOCK_STREAM sockets created with socketpair and used with send/recv