Hi,
On Tue, Sep 8, 2015 at 11:44 AM, Yicong Huang wrote:
> In main thread:
> rpython_startup_code();
> pypy_init_threads();
> res = pypy_setup_home(..);
>
> And in other worker thread, after main thread do the initilization:
> pypy_thread_attach();
Yes, that's how it should be.
> Will there any
Great thanks Armin!
I found out we did call python code from different theads.
Here are my understanding, please correct me if I am wrong:
In main thread:
rpython_startup_code();
pypy_init_threads();
res = pypy_setup_home(..);
And in other worker thread, after main thread do the initilization:
py
Hi,
On Tue, Sep 8, 2015 at 9:20 AM, Yicong Huang wrote:
> Here are the output of gdb "info threads". We didn't call
> "pypy_init_threads()" or "pypy_thread_attach()" in the code.
Well, then. Read again the documentation for these two functions: you
need to call them if your program is going to
Here are the output of gdb "info threads". We didn't call
"pypy_init_threads()" or "pypy_thread_attach()" in the code.
(gdb) info threads
Id Target Id Frame
132 Thread 0x414ea940 (LWP 32385) 0x003472ad4d98 in epoll_wait ()
from /lib64/libc.so.6
131 Thread 0x413e9940 (LWP 32384
Hi Yicong,
On Tue, Sep 8, 2015 at 5:07 AM, Yicong Huang wrote:
>0x7f27ff816b6a <+42>:66 48 8d 3d 8e b3 2f 01 data16 lea
> 0x12fb38e(%rip),%rdi# 0x7f2800b11f00
>0x7f27ff816b72 <+50>:66 66 48 e8 6e ec cf ff data16 data16 callq
> 0x7f27ff5157e8 <__tls_get_addr@plt>
>
Unfortunatelly, I still could not make a simple case to reproduce the issue.
However, we observed the same issue happen several times and core dump
generated in the application these days.
I used gdb to show the disassemble:
(gdb) disassemble /rm
Dump of assembler code for function rpyvmprof_f_pypy
that's certainly a bug. Would be very good to get some sort of info.
Can you do PYPYLOG=jit-log-noopt:log as an environment variable and
send us the file "log" (it might be huge)
On Thu, Sep 3, 2015 at 2:58 AM, Christian Walder
wrote:
> Hello,
>
> I'm running into a segmentation fault on pypy.
>
Hello,
I'm running into a segmentation fault on pypy.
Is the attached OS X crash report useful for diagnosing the problem?
I haven't succeeded in making a minimal example of this issue, as it occurs
in the middle of a complex program, and the same program even runs
correctly when processing a sm
Hi Yicong,
On 31 August 2015 at 11:29, Yicong Huang wrote:
> Yes.
Ok. Fwiw, it's unlikely we can figure out what is wrong without being
able to reproduce the crash ourselves...
Armin
___
pypy-dev mailing list
[email protected]
https://mail.python.
Hi Yicong,
On 31 August 2015 at 11:00, Yicong Huang wrote:
> pypy_execute_source()
Did you call rpython_startup_code() and pypy_setup_home() before?
Armin
___
pypy-dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-dev
Here is the line that causes the segfault:
https://github.com/shoebot/shoebot/blob/shoebot-gtk3-pgi/shoebot/sbot.py#L76
from shoebot.grammar import DrawBot, NodeBot
If I change it to only import one of these then it doesn't segfault. S++
On Wednesday, January 7, 2015 8:57 PM, Stuart Axon
Done
https://bitbucket.org/pypy/pypy/issue/1955/segfault-on-running-program
S++
On Wednesday, January 7, 2015 8:45 PM, Amaury Forgeot d'Arc
wrote:
Hi,
Please file a bug at https://bitbucket.org/pypy/pypy/issuesAlso, please run
"bt" in gdb to show the full stack of the failure.
Hi,
Please file a bug at https://bitbucket.org/pypy/pypy/issues
Also, please run "bt" in gdb to show the full stack of the failure.
2015-01-07 16:06 GMT+01:00 Stuart Axon :
> Hi,
>I'm running pypy 2.4.0 on Ubuntu Utopic.
>
> Running the pypy works OK (though it outputs 'trusty' weirdly):
>
>
Hi, I'm running pypy 2.4.0 on Ubuntu Utopic.
Running the pypy works OK (though it outputs 'trusty' weirdly):
$ pypyPython 2.7.8 (2.4.0+dfsg-1~ppa2+trusty, Sep 25 2014, 04:35:04)[PyPy
2.4.0 with GCC 4.8.2] on linux2Type "help", "copyright", "credits" or "license"
for more information.
Runn
On Fri, Jan 20, 2012 at 4:57 PM, Joseph Javier Perla
wrote:
> I wrote several other missing methods (np.log, np.diag, np.concatenate) and
> now I have the full program working. I would like to add these other
> features as well. (Also, np.sum() should be able to do element-wise sum of
> a genera
I wrote several other missing methods (np.log, np.diag, np.concatenate) and
now I have the full program working. I would like to add these other
features as well. (Also, np.sum() should be able to do element-wise sum of
a generator of n-dimensional arrays.)
But, now I get a segfault. I was won
16 matches
Mail list logo
