Camelia, the Perl 6 bug

IRC log for #padre, 2013-09-24

| Channels | #padre index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:18 asarch joined #padre
01:41 Plecto joined #padre
02:38 Plecto hi all
02:39 Plecto do you know how can I tell Padre to reopen last opened files?
02:46 Plecto found it!!!
04:00 sewi joined #padre
06:34 sugar joined #padre
07:20 dod joined #padre
07:51 Plecto joined #padre
07:59 Di-ima joined #padre
08:17 dod joined #padre
11:42 dod joined #padre
13:30 asarch joined #padre
13:43 itcharlie joined #padre
13:53 Plecto joined #padre
13:54 Plecto joined #padre
13:54 Plecto bowtie: hi
13:55 dod joined #padre
14:02 Plecto bowtie: hi
14:08 itcharlie Plecto:  you got a question?
14:24 Plecto itcharlie: hi
14:25 itcharlie hello Plecto
14:25 Plecto I have Padre 0.98 installed on Mac OSX 10.8.5
14:25 Plecto (but the issue also appears in the trunk version)
14:26 Plecto debugging with output in an external window causes Padre to freeze
14:26 Plecto in the external window
14:26 Plecto I see the following output
14:27 shadowpaste "Plecto" at 217.168.150.38 pasted "Debug" (9 lines) at http://paste.scsys.co.uk/269771
14:27 Plecto this is the file I'm trying to debug /Volumes/HD_2/Dati/Dev/Perl​/Educon2013/scripts/main.pl
14:32 Plecto itcharlie: you there?
14:50 itcharlie hmm
14:54 itcharlie ok so in trunk there is the Debug client
14:54 Plecto itcharlie: no idea?
14:54 itcharlie oh sorry
14:54 itcharlie I mean I am looking at the code.
14:54 itcharlie trunk code in padre
14:54 itcharlie it sets :  local $OUTPUT_AUTOFLUSH = 1;
14:55 itcharlie but you are setting it on your main.pl script
14:55 itcharlie on line 6
14:55 Plecto I have it as a command line in the script
14:55 Plecto right
14:56 Plecto what is strange is that in the external window I'm able to see the output of the script in NON-debug mode
14:56 Plecto I mean, when I run it without debugging it
14:57 Plecto also, debug works if I set to show output in the output pane
14:57 Plecto dod: hi
14:57 itcharlie ok
14:58 Plecto found a solution?
14:58 itcharlie no I am reading code.
14:58 itcharlie trying to get familiar with the setup
14:59 Plecto but looking for a solution to my problem?
14:59 itcharlie yes
14:59 Plecto :)
15:03 bowtie_ joined #padre
15:05 itcharlie hmm
15:06 itcharlie so I ran debugger in trunk
15:06 itcharlie and ran into same problem.
15:06 itcharlie error I get is
15:06 itcharlie An existing connection was forcibly closed by the remote host. at C:/Users/cgonz
15:06 itcharlie alez/Desktop/padre/Padre/lib​/Padre/Wx/Panel/Debugger.pm line 1192.
15:07 Plecto output in external window?
15:07 itcharlie yes
15:08 Plecto does the debugger works if you uncheck that option, so that the output of the debugger goes in the output pane?
15:16 bowtie_ itcharlie: are you at r19788
15:16 botbot Changeset #19788 http://padre.perlide.org/trac/changeset/19788
15:18 itcharlie Plecto:  yes
15:19 itcharlie bowtie_:  I was trying to help Plecto with an issue he is having with the debugger outputing to external window cause it to freeze padre
15:20 Plecto bowtie_: the problem of the bedug freezing when output is set to go to external window also appears for r19788
15:20 botbot Changeset #19788 http://padre.perlide.org/trac/changeset/19788
15:21 Plecto itcharlie: what version of Padre are you using?
15:21 itcharlie I can reproduce problem in Win 7   and yes I am up to r19788
15:21 botbot Changeset #19788 http://padre.perlide.org/trac/changeset/19788
15:21 itcharlie I am using Trunk
15:22 Plecto bowtie_: I think we can agree this is verified issue now
15:22 bowtie_ itcharlie: I was just interested in your 'forcibly closed by the remote host' issue hence Q is your trunk up to date, ie for the following -> http://padre.perlide.org/trac/changeset/19783
15:23 Plecto itcharlie: I have applied that fix and it allows me to see output in the output pane but it does not resolve the issue when external window is selected
15:24 Plecto itcharlie: did you apply the fix thereby specified?
15:26 itcharlie The fix is already in trunk for me. I still see the issue
15:27 itcharlie let me close and start padre again
15:31 itcharlie Yes same problem
15:31 itcharlie no more ip hanging error though thanks for clarifying bowtie_
15:33 itcharlie something unrelated:
15:33 itcharlie Unrecognized escape \U passed through in regex; marked by <-- HERE in m/^ C:\U <
15:33 itcharlie -- HERE sers\cgonzalez\Desktop / at C:/Users/cgonzalez/Desktop/padre/Padre/lib/P
15:33 itcharlie adre/Wx/Panel/Breakpoints.pm line 361.
15:35 Plecto bowtie_: any idea?
15:38 itcharlie seems like the debugging output will always happen on the output pane
15:39 itcharlie even if I select it to display on external window
15:41 Plecto itcharlie: nope, if I select the external window, the debugger freezes
15:41 Plecto itcharlie: does this happen to you too?
15:43 itcharlie no. The debugger info is still displayed in the output pane
15:43 itcharlie no freezing this time.
15:43 Plecto uhm
15:44 Plecto can you make sure you have selected external window for output?
15:44 Plecto bowtie_: is it possible at all to have debug output in an external wondow in Padre?
15:46 itcharlie Plecto:  just to confirm. I go to Tools -> Preferences -> Language -  Perl 5 -> click checbox-> use external window for execution
15:47 Plecto ok, then save, exit and reopen Padre just to be sure the option os read
15:50 itcharlie Yes still the same Plecto
15:51 itcharlie still have the same behavior. I guess its different for windows
15:51 itcharlie ??
15:51 Plecto ok, so bowtie_ should tell us if it is possible at all to have debug output in an external window
16:04 sewi joined #padre
16:17 Plecto itcharlie: but do you see the external window opening when you select external window for output and start debug?
16:23 itcharlie Yes
16:23 itcharlie The external window opens
16:23 itcharlie it just doesn't display anything
16:24 Plecto instead I see this:  http://paste.scsys.co.uk/269771
16:25 Plecto bowtie_: do you see any output in the external window during debug, if you select output to go to external window?
16:28 itcharlie Plecto:  is the external window a terminal?
16:28 Plecto yes
16:28 itcharlie and the output from the external window shows the text in the link?
16:28 Plecto the same in which I can see correct output when I run a script instead of debuging it
16:28 Plecto yes
16:28 itcharlie then I think you are fine.
16:29 itcharlie external window should be a terminal window
16:29 itcharlie from what I see
16:29 Plecto yes, but 1) you don't see similar output 2) in my case the debugger freezes
16:30 Plecto here it seems they get similar output, but the debugger should not freeze http://www.perlmonks.org/?node_id=750710
16:42 bowtie_ it is intended that the user can choose where the output goes to a, output-panel b, external window
16:43 bowtie_ itcharlie: just taking a look at Wx/Panel/Breakpoints.pm line 361
16:45 itcharlie k
16:48 Plecto joined #padre
16:48 Plecto bowtie_: so the behavior itcharlie is observing is not correct
16:49 Plecto bowtie_: I mean, he is not seeing the output of the debug in an external window
16:49 Plecto but in the internal panel
16:49 Plecto even if he has selected the external window output option
16:50 Plecto bowtie_: does this output tells you anithing?  http://paste.scsys.co.uk/269771
16:51 bowtie_ when you enable debug in Padre, you get three new panels, left - breakpoints, right - debugger, bottom - debugger output, plus you can have STDOUT in output-panel or external
16:53 bowtie_ see -> http://padre.perlide.org/trac/wi​ki/Features/Perl5Debugger#slide1 and slide2 for examples
16:56 Plecto bowtie_: cannot see any external window output there, only panes I think
16:56 bowtie_ itcharlie: looks like project_dir is in win32 format, how odd, need to think about that
16:57 dod joined #padre
16:59 bowtie_ Plecto: try again with a simple perl app, also did you check out -> http://irclog.perlgeek.de/​padre/2013-09-19#i_7606257
17:03 itcharlie bowtie I think there is a module that will stringify the path for both unix or linux file path
17:03 itcharlie maybe we can use that?
17:04 itcharlie I think its Path::Class
17:04 Plecto bowtie_: can you tell me if this output looks fine to you?  http://paste.scsys.co.uk/269771
17:06 itcharlie Plecto: are you familair with the perl debugger via commandline?
17:08 itcharlie asking cause I wanted to know if your question was related to "Hey I got this output but I don't know if this is what I should expect from perl debugger?"
17:08 itcharlie the output you see there is from the perl debugger.
17:11 bowtie_ itcharlie: let me have a think about it, I will get back to you later
17:12 Plecto itcharlie: nope, I'm not familiar sorry, this is why I asked if the output I see is correct or strange
17:13 Plecto itcharlie: for example, should I hit any key to let the debugger proceed and do not freeze?
17:13 Plecto itcharlie: maybe that window just need some input and the debugger does not freezes, I don't know
17:18 Plecto itcharlie: any hint?
17:21 Plecto ?
17:24 bowtie_ Plecto: Assumption you are aware of this: ​http://perldoc.perl.org/perldebug.html
17:24 bowtie_ Plecto: see Pro Perl Debugging ​http://www.apress.com/9781590594544 It's a nice text,
17:26 itcharlie but know that the debugger options need to be set via the Padre Debugger right?
17:27 itcharlie look at 'n' for example
17:28 itcharlie if you hover over the {} buttons via the padre debugger you can see which one is n or s
17:28 itcharlie n  stands for next  while s stands for single step
17:29 itcharlie oh he left
17:37 bowtie_ itcharlie: do you have access to Tools->Padre Dev Tools->Evaluate Expression
17:38 bowtie_ itcharlie: can you run the above and evaluate -> Padre::Current->document->{project_dir}
17:39 bowtie_ itcharlie: this way I can see if the internal Padre is in win32 or unix format, thanks
17:42 itcharlie nope
17:42 itcharlie Padre Dev tools is a plugin?
17:42 itcharlie ah
17:43 itcharlie 0  'C:\\Users\\cgonzalez\\Desktop'
17:43 itcharlie I see this is a nice plugin
17:43 bowtie_ itcharlie: yes it's one of adams :)
17:44 itcharlie bowtie_ I am running padre in Win7
17:44 itcharlie coolio
17:44 itcharlie looks very helpful for padre dev
17:45 bowtie_ itcharlie: that's one half of line 361, do you fancy taking a look at the other half ?
17:45 itcharlie sure
17:46 bowtie_ itcharlie: you will need pp-cookbook recipe 04, you can then view the stored breakpoints as in -> http://padre.perlide.org/trac/wiki/Fe​atures/Perl5Debugger#DebugBreakpoints
17:55 itcharlie ok just got lost
17:55 itcharlie what do you mean by pp-cookbook recipe 04
17:59 bowtie_ itcharlie: sorry pp eq Padre::Plugin hence -> https://metacpan.org/modul​e/Padre::Plugin::Cookbook
17:59 bowtie_ itcharlie: or if you have full trunk you can do: perl dev -a
18:08 itcharlie hmm
18:08 itcharlie I don't see the breakpoints
18:08 itcharlie so bug.
18:08 itcharlie let me see if I can figure out a way to display them.
18:13 bowtie_ itcharlie: cool, I will let you poke around in the local DB files, ps they are in sqlite format if that helps
18:14 itcharlie ok
18:18 bowtie_ itcharlie: and thanks for this
18:19 itcharlie no problem
18:30 Plecto joined #padre
18:44 itcharlie hey Plecto
18:47 itcharlie brb
19:09 kaare joined #padre
19:48 Lorn joined #padre
19:49 BooK joined #padre
19:50 patspam joined #padre
19:51 itcharlie joined #padre
19:54 garu joined #padre
19:57 Plecto hi itcharlie
20:00 Plecto itcharlie?
20:28 stkowski joined #padre
20:43 chorny joined #padre
21:00 stkowski joined #padre
21:12 TimK joined #padre
21:24 Plecto hello all
21:24 Plecto any idea of the following error?
21:24 Plecto Debug: wxMacLaunch Bad bundle: /usr/local/perl/site/lib/auto/Wx/​wxPerl.app/Contents/MacOS/wxPerl
21:26 shadowpaste joined #padre

| Channels | #padre index | Today | | Search | Google Search | Plain-Text | summary