[pypy-dev] PYPYLOG

2022-03-22 Thread Aksam Lwanga
Hey. am confused about the debugging variable for PYPYLOG, have set its value, am trying to run the benchmark so that I can get some insights on how to use it in the future, however when I compile my file it doesn't show me the output file, do I need to set any other thing apart from the PYPYLOG en

Re: [pypy-dev] PYPYLOG - get two at once jit-backend-dump+jit-backend-addr

2016-12-12 Thread Yury V. Zaytsev
On Mon, 12 Dec 2016, Armin Rigo wrote: Hi, On 12 December 2016 at 07:07, Yury V. Zaytsev wrote: Separate by comma as explained in the documentation that I've linked? PYPYLOG=jit-backend-dump:shubha.log,jit-backend-addr:shubha.log No, only one file name: PYPYLOG=jit-backend-dump,jit

Re: [pypy-dev] PYPYLOG - get two at once jit-backend-dump+jit-backend-addr

2016-12-12 Thread Armin Rigo
Hi, On 12 December 2016 at 07:07, Yury V. Zaytsev wrote: > Separate by comma as explained in the documentation that I've linked? > > PYPYLOG=jit-backend-dump:shubha.log,jit-backend-addr:shubha.log No, only one file name: PYPYLOG=jit-backend-dump,jit-backend-addr:shubha.log Or use a pre

Re: [pypy-dev] PYPYLOG - get two at once jit-backend-dump+jit-backend-addr

2016-12-11 Thread Yury V. Zaytsev
On Mon, 12 Dec 2016, Shubha Ramani via pypy-dev wrote: I can do export PYPYLOG=jit-backend-dump:shubha.log and I can do export PYPYLOG=jit-backend-addr:shubha.log while running the attached file which computes Fibonacci numbers. I run the script just by pypy fib.py and I did add the requisite

Re: [pypy-dev] PYPYLOG - get two at once jit-backend-dump+jit-backend-addr

2016-12-11 Thread Shubha Ramani via pypy-dev
A search on "debug_start" in the pypy source code base reveals many other log options.So how do you include multiple in one file ?     On Sunday, December 11, 2016 7:33 PM, Shubha Ramani wrote: I can do  export PYPYLOG=jit-backend-dump:shubha.log and I can do  export PYPYLOG=ji

[pypy-dev] PYPYLOG - get two at once jit-backend-dump+jit-backend-addr

2016-12-11 Thread Shubha Ramani via pypy-dev
I can do  export PYPYLOG=jit-backend-dump:shubha.log and I can do  export PYPYLOG=jit-backend-addr:shubha.logwhile running the attached file which computes Fibonacci numbers. I run the script just by pypy fib.py and I did addthe requisite jitdriver and merge_point stuff. My question is, is there

Re: [pypy-dev] PYPYLOG and colon as a special character

2014-06-13 Thread Armin Rigo
Hi Christian, On 13 June 2014 16:21, Christian Hudon wrote: > The colon character is valid in paths in Windows (because of the drive > letter), but not in filenames (it's used for supporting different streams, > which hardly anyone uses). So doing that check on > os.path.basename(os.getenv("PYPYL

Re: [pypy-dev] PYPYLOG and colon as a special character

2014-06-13 Thread Matti Picus
We discussed this on IRC and decided to add a workaround, '+filename' will be handled like 'filename' Matti On 13/06/2014 5:21 PM, Christian Hudon wrote: The colon character is valid in paths in Windows (because of the drive letter), but not in filenames (it's used for supporting different str

Re: [pypy-dev] PYPYLOG and colon as a special character

2014-06-13 Thread Christian Hudon
The colon character is valid in paths in Windows (because of the drive letter), but not in filenames (it's used for supporting different streams, which hardly anyone uses). So doing that check on os.path.basename(os.getenv("PYPYLOG")) should work under Windows also. Of course, I didn't check t

[pypy-dev] PYPYLOG and colon as a special character

2014-06-13 Thread Matti Picus
if PYPYLOG is a filename, we log to it (except debug_print) if PYPYLOG is :filename, we log debug_print as well if PYPYLOG is section:filename, we log only that section But : is a valid char for filename on windows, so something like PYPYLOG=C:\TEMP\log.log does the wrong thing, and even worse, d