Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Jun 2008 03:16:00 +0530
From:      wahjava.ml@gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=)
To:        Joe Marcus Clarke <marcus@marcuscom.com>
Cc:        freebsd-gnome@freebsd.org
Subject:   Re: devel/py-gobject: segfaulting on gobject.markup_escape_text()
Message-ID:  <863amx6xnr.fsf@chateau.d.lf>
In-Reply-To: <1214677587.86194.10.camel@shumai.marcuscom.com> (Joe Marcus Clarke's message of "Sat, 28 Jun 2008 14:26:27 -0400")
References:  <86hcbhcis9.fsf@chateau.d.lf> <op.udbz4kkr9aq2h7@mezz.mezzweb.com> <20080626023430.GA9249@chateau.d.lf> <1214677587.86194.10.camel@shumai.marcuscom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

,--- Joe Marcus Clarke writes:

[snip]

| I agree with your analysis, but I cannot reproduce, and I cannot see
| where the code is wrong.  The call to PyArg_ParseTupleAndKeywords()
| looks okay, so text_in should point to right address.  Have you built
| Python with any non-default OPTIONS?  If not, have you reported this bug
| upstream?

I've not reported this bug upstream.

=2D---8<----8<----
abbe [~] chateau% cat /var/db/ports/python25/options=20
# This file is auto-generated by 'make config'.
# No user-servicable parts inside!
# Options for python25-2.5.2_2
_OPTIONS_READ=3Dpython25-2.5.2_2
WITH_THREADS=3Dtrue
WITHOUT_HUGE_STACK_SIZE=3Dtrue
WITH_UCS4=3Dtrue
WITH_PYMALLOC=3Dtrue
WITH_IPV6=3Dtrue
WITH_FPECTL=3Dtrue
abbe [~] chateau% cat /etc/make.conf |fgrep WITH
WITH_IPV6=3Dtrue
WITH_THREADS=3Dtrue
=2D--->8---->8----

I'd earlier tried toggling WITH_PYMALLOC, and WITH_UCS4 options, but
result was same.

And now, I wiped off /var/db/ports/python25/options and reinstalled
'lang/python25' with no options explicitly chosen (WITH_IPV6,
WITH_THREADS, WITH_UCS4, WITH_PYMALLOC are ON by default in Makefile),
and it still segfaulted.

Should I create a PR in FreeBSD, and also reported this to upstream,
hmm..? I wish if any amd64 users can verify this bug on their box ? I
tested it on my 2 Intel EM64T boxen (Pentium4, Core2 Duo) and both
segfaulted at same point.

Thanks
=2D-=20
Ashish Shukla =E0=A4=86=E0=A4=B6=E0=A5=80=E0=A4=B7 =E0=A4=B6=E0=A5=81=E0=A4=
=95=E0=A5=8D=E0=A4=B2                      http://wahjava.wordpress.com/
=C2=B7-- =C2=B7- =C2=B7=C2=B7=C2=B7=C2=B7 =C2=B7--- =C2=B7- =C2=B7=C2=B7=C2=
=B7- =C2=B7- =C2=B7--=C2=B7-=C2=B7 --=C2=B7 -- =C2=B7- =C2=B7=C2=B7 =C2=B7-=
=C2=B7=C2=B7 =C2=B7-=C2=B7-=C2=B7- -=C2=B7-=C2=B7 --- --

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkhmsRgACgkQHy+EEHYuXnTZhwCg6bZTbIkn42qY3vAADFQSmstO
7kAAoNxHglE7UkL89trHOAZrmzw/qvS3
=gmL7
-----END PGP SIGNATURE-----
--=-=-=--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?863amx6xnr.fsf>