From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-07-11
Date: Sat, 12 Jul 2014 12:07:42 +0200 [thread overview]
Message-ID: <20140712100741.GB3582@free.fr> (raw)
In-Reply-To: <20140712095548.GA3582@free.fr>
Thomas, All,
On 2014-07-12 11:55 +0200, Yann E. MORIN spake thusly:
> On 2014-07-12 08:30 +0200, Thomas Petazzoni spake thusly:
> > arm | python-2.7.8 | NOK | http://autobuild.buildroot.net/results/10f268cd55f16ee53f4c5e17e1248b0a1820f6ea/
>
> Reproduced, investigating...
OK, the sqlite3 extension has a bug. It has code like:
---8<---
void _pysqlite_final_callback(sqlite3_context* context)
{
PyObject* function_result;
PyObject** aggregate_instance;
int ok;
#ifdef WITH_THREAD
PyGILState_STATE threadstate;
threadstate = PyGILState_Ensure();
#endif
aggregate_instance = (PyObject**)sqlite3_aggregate_context(context, sizeof(PyObject*));
if (!*aggregate_instance) {
goto error;
}
[......]
error:
#ifdef WITH_THREAD
PyGILState_Release(threadstate);
#endif
}
---8<---
So, they are doing right to cleanup in case of error. But when threads
are not available, the function is like:
---8<---
void _pysqlite_final_callback(sqlite3_context* context)
{
PyObject* function_result;
PyObject** aggregate_instance;
int ok;
aggregate_instance = (PyObject**)sqlite3_aggregate_context(context, sizeof(PyObject*));
if (!*aggregate_instance) {
goto error;
}
[......]
error:
}
---8<---
And indeed, there's nothing after the 'error' label. And gcc does not
like that:
connection.c:785:1: error: label@end of compound statement
So, the solution is relatively easy: add a dummy statement after the
label:
error:
;
}
And it works, now. I'll submit a patch soonish...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-07-12 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-07-11 Thomas Petazzoni
2014-07-12 9:55 ` Yann E. MORIN
2014-07-12 10:07 ` Yann E. MORIN [this message]
2014-07-12 22:21 ` Yann E. MORIN
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=20140712100741.GB3582@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox