So I added my first buildbot yesterday (for FreeBSD and I hope to add a few
more different BSD ones to the fray) and I see that it is failing in the
test_curses part.
I tracked it by hand and somewhere along the test it segfaults. The
resulting coredump is not really helpful.
(gdb) bt
#0 0x281aa
> So I added my first buildbot yesterday (for FreeBSD and I hope to add a few
> more different BSD ones to the fray) and I see that it is failing in the
> test_curses part.
>
> I tracked it by hand and somewhere along the test it segfaults. The
> resulting coredump is not really helpful.
>
> (gdb
-On [20080308 12:08], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>If you want to ask for help, that's probably something for the FreeBSD
>lists. Unfortunately, the FreeBSD threads library is notorious for
>crashing, hanging, and doing other unpleasant things to Python.
I think I can manage the F
> One result I get is this:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x8173000 (LWP 100121)]
> 0x28ac4102 in PyCurses_getsyx (self=0x0)
> at /usr/home/asmodai/projects/python/Modules/_cursesmodule.c:1770
> 1770 getsyx(y, x);
>
> Is a value of 0x0 va
-On [20080309 20:23], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>If it's similar on FreeBSD, the only reason why this
>could break is that newscr is NULL.
This is what I get:
do {
if(newscr->_leaveok)
(y) = (x) = -1;
else
((y) = ((newscr) ? (newscr)->_cury : (
> (gdb) print newscr
> $1 = (WINDOW *) 0x0
>
> So it seems that the newscr variable is indeed a NULL.
So this now *is* a FreeBSD/ncurses expert's question.
I don't think this is supposed to happen; newscr should
become non-NULL when initscr is called, and should remain
that way throughout.
Regar
-On [20080309 23:59], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>So this now *is* a FreeBSD/ncurses expert's question.
>I don't think this is supposed to happen; newscr should
>become non-NULL when initscr is called, and should remain
>that way throughout.
Looking at the other FreeBSD build it
Jeroen Ruigrok van der Werven wrote:
> -On [20080309 23:59], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>> So this now *is* a FreeBSD/ncurses expert's question.
>> I don't think this is supposed to happen; newscr should
>> become non-NULL when initscr is called, and should remain
>> that way thro
-On [20080312 13:30], Andrew MacIntyre ([EMAIL PROTECTED]) wrote:
>test_curses on its own passes on my FreeBSD 6.3 box. It segfaults when
>run in the context of a full regression test though.
So it does for my 6.3-STABLE.
But 6.2-RELEASE goes through the entire regression though. I need to check
-On [20080309 23:59], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>So this now *is* a FreeBSD/ncurses expert's question.
Actually, given my recent results and discussion with Thomas Dickey I am not
so sure.
Some basic debugging I did with Georg Brandl led to this:
comment the requires('curses')
> Actually, given my recent results and discussion with Thomas Dickey I am not
> so sure.
Even if there is a bug in the test or in Python that causes newscr to
become NULL - why does that not show up in other releases, or on other
systems?
> Thomas mentioned after seeing an ltrace:
>
> Perhaps i
-On [20080329 18:37], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>Even if there is a bug in the test or in Python that causes newscr to
>become NULL - why does that not show up in other releases, or on other
>systems?
I have been breaking my head about that as well. But then again it is just
as
12 matches
Mail list logo
