All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: Randolph Chung <randolph@tausq.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] nslookup segmentation fault
Date: Tue, 26 Feb 2002 16:41:30 -0500	[thread overview]
Message-ID: <20020226164130.B5289@systemhalted> (raw)
In-Reply-To: <20020226194150.GB11598@tausq.org>; from randolph@tausq.org on Tue, Feb 26, 2002 at 11:41:51AM -0800

> Neat....
> 
> Here's part of Dennis' strace of nslookup:
> > m4450dmf:/etc# strace nslookup athp.hp.com
> [...]
> > rt_sigprocmask(SIG_BLOCK, [HUP INT TERM], NULL, 8) = 0
> > getpid()                                = 22574
> > socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
> > close(3)                                = 0
> > socket(PF_INET6, SOCK_STREAM, 0)        = -1 EAFNOSUPPORT (Address family
> > not su
> > pported by protocol)
> > brk(0)                                  = 0x2f000
> > brk(0x2f030)                            = 0x2f030
> > brk(0x30000)                            = 0x30000
> > brk(0x33000)                            = 0x33000
> > --- SIGSEGV (Segmentation fault) ---
> > +++ killed by SIGSEGV +++
> 
> why is it trying to do ipv6?
> 
> randolph
> -- 


I'm feel worried about what brk() is trying to do.

PF_INET==2 and PF_INET6==10 are only a single bit appart :}
Cosmic radiation maybe?

I'm not sure what is going on. Though I tried to build
Bind 8.3.1 on x86 and if failed (need to look into bits/types).

eventlib.c: In function `__evGetNext':
eventlib.c:298: structure has no member named `fds_bits'
eventlib.c:299: structure has no member named `fds_bits'
eventlib.c:300: structure has no member named `fds_bits'

c.

  reply	other threads:[~2002-02-26 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2F1E6AB90ECAD311943700A0C9E3B1540804ED28@xatl03.atl.hp.com>
2002-02-26 19:41 ` [parisc-linux] nslookup segmentation fault Randolph Chung
2002-02-26 21:41   ` Carlos O'Donell Jr. [this message]
2002-02-26 22:08     ` Jochen Friedrich
2002-02-26 15:09 FAUCHER,DENNIS (HP-USA,ex1)
2002-02-26 15:39 ` Randolph Chung

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020226164130.B5289@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=parisc-linux@parisc-linux.org \
    --cc=randolph@tausq.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.