From 2fd0d6136e613c86a8ca1494475b6d21f4ba97da Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sat, 24 Jul 2010 12:23:41 +0200 Subject: open_issues/elinks: New. --- open_issues/elinks.mdwn | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 open_issues/elinks.mdwn diff --git a/open_issues/elinks.mdwn b/open_issues/elinks.mdwn new file mode 100644 index 00000000..ff1bd46a --- /dev/null +++ b/open_issues/elinks.mdwn @@ -0,0 +1,24 @@ +[[!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 + + In elinks/src/network/state.h, there is an assumption that values of errno are between 0 and 100000. Now looking at glibc-2.5/sysdeps/mach/hurd/bits/errno.h, I see that you're using values outside this range. Have there been problems because of this? + eeerf + I had never seen a program assuming that + that sucks + It can be fixed, but that'd require some work, so I'd like to first have a clear idea of the effects. + fixed where ? + in elinks + k + by allocating just one number from our enum connection_state for system errors, and then stashing the errno value in a separate variable. + Anyway, if you see this cause any user-visible bugs in ELinks, please report. -- cgit v1.2.3