From owner-freebsd-threads@FreeBSD.ORG Mon Aug 4 05:05:02 2008
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1CAB41065674
for <freebsd-threads@freebsd.org>; Mon, 4 Aug 2008 05:05:02 +0000 (UTC)
(envelope-from gofdt-freebsd-threads@m.gmane.org)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
by mx1.freebsd.org (Postfix) with ESMTP id B7B978FC0C
for <freebsd-threads@freebsd.org>; Mon, 4 Aug 2008 05:05:01 +0000 (UTC)
(envelope-from gofdt-freebsd-threads@m.gmane.org)
Received: from list by ciao.gmane.org with local (Exim 4.43)
id 1KPrQX-00039B-Of
for freebsd-threads@freebsd.org; Mon, 04 Aug 2008 04:12:09 +0000
Received: from 78-0-90-58.adsl.net.t-com.hr ([78.0.90.58])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <freebsd-threads@freebsd.org>; Mon, 04 Aug 2008 04:12:09 +0000
Received: from ivoras by 78-0-90-58.adsl.net.t-com.hr with local (Gmexim 0.1
(Debian)) id 1AlnuQ-0007hv-00
for <freebsd-threads@freebsd.org>; Mon, 04 Aug 2008 04:12:09 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-threads@freebsd.org
From: Ivan Voras <ivoras@freebsd.org>
Date: Mon, 04 Aug 2008 06:11:58 +0200
Lines: 39
Message-ID: <g75vif$6pa$1@ger.gmane.org>
References: <c62705fb0808021323u2f2c7d59n5c1b474720b854e0@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enig82DCB7DFF2070D9DBAE8FB5A"
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: 78-0-90-58.adsl.net.t-com.hr
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
In-Reply-To: <c62705fb0808021323u2f2c7d59n5c1b474720b854e0@mail.gmail.com>
X-Enigmail-Version: 0.95.6
Sender: news <news@ger.gmane.org>
Subject: Re: Need Help on "threads/110306: apache 2.0 segmentation violation
when calling gethostbyname"
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Aug 2008 05:05:02 -0000
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig82DCB7DFF2070D9DBAE8FB5A
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Jeff Mo wrote:
> Hi ,
>=20
> Can anyone nicely explain a little bit about what does "ServerName is n=
ot
> defined
> in httpd.conf." mean in the following sentence from bug description?
>=20
> "The problem happens if php module is loaded and ServerName is not defi=
ned
> in httpd.conf."
You are not looking for the trivial answer? ("ServerName" is a=20
configuration item in httpd.conf). If ServerName is not set, Apache will =
try to guess the host's FQDN by various tricks, including reverse DNS=20
lookup on its IP.
--------------enig82DCB7DFF2070D9DBAE8FB5A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIloGPldnAQVacBcgRAhBaAKDSkwyKkDdYPSImkXqC1DYHUu1qiACfVpPM
PVtXxbnp31IPMSiwB/ImLfE=
=jW2i
-----END PGP SIGNATURE-----
--------------enig82DCB7DFF2070D9DBAE8FB5A--
From owner-freebsd-threads@FreeBSD.ORG Mon Aug 4 11:07:03 2008
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C78A6106566B
for <freebsd-threads@FreeBSD.org>; Mon, 4 Aug 2008 11:07:03 +0000 (UTC)
(envelope-from owner-bugmaster@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
[IPv6:2001:4f8:fff6::28])
by mx1.freebsd.org (Postfix) with ESMTP id B7CB28FC16
for <freebsd-threads@FreeBSD.org>; Mon, 4 Aug 2008 11:07:03 +0000 (UTC)
(envelope-from owner-bugmaster@FreeBSD.org)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m74B738K082229
for <freebsd-threads@FreeBSD.org>; Mon, 4 Aug 2008 11:07:03 GMT
(envelope-from owner-bugmaster@FreeBSD.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m74B73SR082225
for freebsd-threads@FreeBSD.org; Mon, 4 Aug 2008 11:07:03 GMT
(envelope-from owner-bugmaster@FreeBSD.org)
Date: Mon, 4 Aug 2008 11:07:03 GMT
Message-Id: <200808041107.m74B73SR082225@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: gnats set sender to
owner-bugmaster@FreeBSD.org using -f
From: FreeBSD bugmaster <bugmaster@FreeBSD.org>
To: freebsd-threads@FreeBSD.org
Cc:
Subject: Current problem reports assigned to freebsd-threads@FreeBSD.org
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Aug 2008 11:07:04 -0000
Current FreeBSD problem reports
Critical problems
S Tracker Resp. Description
--------------------------------------------------------------------------------
s threa/76690 threads fork hang in child for -lc_r
1 problem total.
Serious problems
S Tracker Resp. Description
--------------------------------------------------------------------------------
s threa/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVTIMEO socket o
s threa/24632 threads libc_r delicate deviation from libc in handling SIGCHL
s bin/32295 threads pthread(3) dont dequeue signals
s threa/34536 threads accept() blocks other threads
s threa/39922 threads [threads] [patch] Threaded applications executed with
s threa/48856 threads Setting SIGCHLD to SIG_IGN still leaves zombies under
s threa/49087 threads Signals lost in programs linked with libc_r
o threa/70975 threads [sysvipc] unexpected and unreliable behaviour when usi
o threa/72953 threads fork() unblocks blocked signals w/o PTHREAD_SCOPE_SYST
o threa/75273 threads FBSD 5.3 libpthread (KSE) bug
o threa/75374 threads pthread_kill() ignores SA_SIGINFO flag
s threa/76694 threads fork cause hang in dup()/close() function in child (-l
o threa/79683 threads svctcp_create() fails if multiple threads call at the
o threa/80435 threads panic on high loads
o threa/83914 threads [libc] popen() doesn't work in static threaded program
s threa/84483 threads problems with devel/nspr and -lc_r on 4.x
s threa/94467 threads send(), sendto() and sendmsg() are not correct in libc
s threa/100815 threads FBSD 5.5 broke nanosleep in libc_r
o threa/101323 threads fork(2) in threaded programs broken.
o threa/103975 threads Implicit loading/unloading of libpthread.so may crash
o threa/110636 threads [request] gdb(1): using gdb with multi thread applicat
o threa/118715 threads kse problem
o threa/121336 threads lang/neko threading ok on UP, broken on SMP (FreeBSD 7
23 problems total.
Non-critical problems
S Tracker Resp. Description
--------------------------------------------------------------------------------
s threa/30464 threads pthread mutex attributes -- pshared
s threa/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwrite() need wra
s threa/40671 threads pthread_cancel doesn't remove thread from condition qu
s threa/69020 threads pthreads library leaks _gc_mutex
o threa/79887 threads [patch] freopen() isn't thread-safe
o threa/80992 threads abort() sometimes not caught by gdb depending on threa
o threa/110306 threads apache 2.0 segmentation violation when calling gethost
o threa/115211 threads pthread_atfork misbehaves in initial thread
o threa/116181 threads /dev/io-related io access permissions are not propagat
o threa/116668 threads can no longer use jdk15 with libthr on -stable SMP
o threa/122923 threads 'nice' does not prevent background process from steali
o kern/126128 threads [patch] pthread_condattr_getpshared is broken
12 problems total.
From owner-freebsd-threads@FreeBSD.ORG Mon Aug 4 19:39:39 2008
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B0FF81065675
for <freebsd-threads@freebsd.org>; Mon, 4 Aug 2008 19:39:39 +0000 (UTC)
(envelope-from dixit@netapp.com)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37])
by mx1.freebsd.org (Postfix) with ESMTP id 9D0EB8FC1E
for <freebsd-threads@freebsd.org>; Mon, 4 Aug 2008 19:39:39 +0000 (UTC)
(envelope-from dixit@netapp.com)
X-IronPort-AV: E=Sophos;i="4.31,306,1215414000"; d="scan'208";a="24391775"
Received: from smtp1.corp.netapp.com ([10.57.156.124])
by mx2-out.netapp.com with ESMTP; 04 Aug 2008 12:39:38 -0700
Received: from dixit-lxp.nane.netapp.com (gpowelltp.nane.netapp.com
[10.97.16.81] (may be forged))
by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id
m74JdcP4018032
for <freebsd-threads@freebsd.org>; Mon, 4 Aug 2008 12:39:38 -0700 (PDT)
Message-ID: <48975AF9.3060204@netapp.com>
Date: Mon, 04 Aug 2008 15:39:37 -0400
From: "Dixit, Amol" <dixit@netapp.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080707)
MIME-Version: 1.0
To: freebsd-threads@freebsd.org
References: <488A213F.70105@netapp.com>
In-Reply-To: <488A213F.70105@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: libpthread and gdbserver
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Aug 2008 19:39:39 -0000
Hi,
I am now linking my sample application with libthr instead of
libpthread, as libthr is the default going forward and it got me past
issues in my previous mail (below).
I had a question regarding FreeBsd libthread_db.
In libthr_db_ops vector (libthr_db.c), we have pt_ta_map_id2thr() and
pt_ta_map_lwp2thr(). The former maps tid to thread_handle and latter
maps pid to tid.
But pt_ta_map_lwp2thr() internally calls pt_ta_map_id2thr() in
libthr_db.c so 'pid to tid' conversion is missing.
If FreeBsd intends to keep it this way, I will have to modify gdbserver
to not use 'pid' to find threads as Linux does.
Can someone shed some light on this? Am I mailing the correct
mailing-list with these queries?
Thanks,
Amol
Dixit, Amol wrote:
> Hi,
> I am attempting to port gdbserver to freebsd (initially only for x86 &
> libpthread) and I need some assistance with libpthread and libthread-db.
> (i) From the code looks like libpthread does not provide any 'thread
> creation event' symbol/address to be looked up by thread-db. I got
> around this by adding a dummy function call before _thread_create
> returned, and that new symbol can be used by thread-db to set
> thread-creation breakpoint (analogous to _thread_bp_create in libthr).
> (ii) Next hurdle is the race between thread-db and libpthread.
> Thread-db tries to access '_thread_list' which is maintained in
> libpthread and will eventually contain the 'initial thread' but this
> list is NULL when thread-db tries to access it early. There is a
> comment before _pthread_create() "It'd be nice to automatically have
> _libpthread_init called on program execution..." which will be helpful
> for thread-db. Currently I am stuck here as thread-db cannot enable
> threading early enough since libpthread is assigning 'initial thread'
> to '_thread_list' lazily.
>
> Am I on the right track on above issues? Any work going on in this area?
> Really appreciate any help on this project.
>
> Thanks,
> Amol
>
>
> _______________________________________________
> freebsd-threads@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-threads
> To unsubscribe, send any mail to
> "freebsd-threads-unsubscribe@freebsd.org"