subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/386791
Title:
libc getaddrinfo crashes if /etc/hosts has very long lines
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/386791/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
t, and it has no relevant changes. (I was unable to set up
a chroot to actually test the current git version, sorry.)
Original bug:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/386791
Reply at: https://bugs.launchpad.net/glibc/+bug/386791/comments/11
--
Has there been any progress on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/386791
Title:
libc getaddrinfo crashes if /etc/hosts has very long lines
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Changed in: glibc
Status: Incomplete => In Progress
--
libc getaddrinfo crashes if /etc/hosts has very long lines
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Changed in: glibc
Status: Confirmed => Incomplete
--
libc getaddrinfo crashes if /etc/hosts has very long lines
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Lars: I just found this was reported more than two years ago, and marked
as invalid. I've just reopened it: bug 103960.
--
libc getaddrinfo crashes if /etc/hosts has very long lines
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a member of Ubuntu
Bugs,
Fibonacci: you are probably right. Please do so. I don't want to do
that, since I don't use network-admin.
--
libc getaddrinfo crashes if /etc/hosts has very long lines
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Shouldn't this bug be reported also to network-admin? Of course, libc
shouldn't crash in the first place even if there are too long lines
(which is the original report), but also, there's no reason for network-
admin to lump all entries into as few lines as possible, creating lines
that long.
--
** Changed in: glibc
Status: Unknown => Confirmed
--
libc getaddrinfo crashes if /etc/hosts has very long lines
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
** Bug watch added: Sourceware.org Bugzilla #10484
http://sourceware.org/bugzilla/show_bug.cgi?id=10484
** Also affects: glibc via
http://sourceware.org/bugzilla/show_bug.cgi?id=10484
Importance: Unknown
Status: Unknown
--
libc getaddrinfo crashes if /etc/hosts has very long line
** Summary changed:
- aMSN crashes when running it twice
+ libc getaddrinfo crashes if /etc/hosts has very long lines
--
libc getaddrinfo crashes if /etc/hosts has very long lines
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a member of Ubuntu
Bugs, w
The problem seems to be that glibc (eglibc is identical in this regard,
it seems) uses alloca when reading the /etc/hosts file, and does not do
the complicated signal handling magic to handle the case when the stack
gets full. The fix would be to rewrite the parsing logic to use safer
memory alloca
** Changed in: eglibc (Ubuntu)
Status: New => Triaged
** Changed in: eglibc (Ubuntu)
Importance: Undecided => Low
--
aMSN crashes when running it twice
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
. Create a line in /etc/hosts at least 4000 characters long (I did not figure
out the exact line length).
2. Re-run the attached program. It will segfault.
3. Remove the long line from hosts.
4. Re-run th eattached program. It will again not segfault.
** Attachment added: "bug-386791.c&quo
Thanks for your package suggestion, hopefully by notifying the right
package maintainers, I can get this bug fixed a bit faster then under
just the generic Ubuntu. Good luck.
** Package changed: ubuntu => eglibc (Ubuntu)
--
aMSN crashes when running it twice
https://bugs.launchpad.net/bugs/38679
I think it's libc6.
--
aMSN crashes when running it twice
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
I am trying to assign this bug to the right package. Do you know what
program is called upon for getaddrinfo?
--
aMSN crashes when running it twice
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The root of the problem is that getaddrinfo("localhost", NULL, NULL,
&result); (which is what aMSN does - both in the official and the SVN
version) causes a segfault in my system. There's no reason it should
cause a segfault, so the bug, as originally stated, is not within aMSN
code.
However, doin
Perhaps you didn't read my original report. The bug is not within the code not
supported by Ubuntu. As it was written in the URL I posted, which you didn't
take the time to read, "this looks to me like they're using a bugged version of
libc or some other library."
Anyway, I tried it with the off
I should also note that if you are able to reproduce this on a version
in Ubuntu, then this is a valid report. If that's the case, then feel
free to reopen the bug.
--
aMSN crashes when running it twice
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a m
As the version you are currently running is not in Ubuntu as you
compiled it directly from source, it is also not supported by Ubuntu,
and thus bug reports cannot be reported against this version.
** Changed in: ubuntu
Status: New => Invalid
--
aMSN crashes when running it twice
https://b
Public bug reported:
I'm using the latest SVN version of aMSN, compiled directly from source. When
running it once, all is fine and dandy; but if I run it again whenever another
instance of the program is running, it will segfault.
I reported it to the aMSN team (see
http://www.amsn-project.net
** Attachment added: "full backtrace"
http://launchpadlibrarian.net/27876610/gdb.txt
--
aMSN crashes when running it twice
https://bugs.launchpad.net/bugs/386791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
23 matches
Mail list logo
