Nuno Furbiz

Home

snmp Walk also crashes on Ubuntu 18.04 x64

I'm glad it has helped you :) Steve On Tue, 11 Sep 2018 at 12:54, Liang Xu mosxl@users.sourceforge.net wrote: Thank you Jan and Steve, I also got the issue fixed with your solution. Hope this issue would be fixed permanently in the future. [bugs:#700] https://sourceforge.net/p/e-p-i-c/bugs/700/ Ticket #698 not solved in EPIC 0.7.5* Status: open Group: v0.7.x Created: Thu May 17, 2018 08:19 PM UTC by Mike Last Updated: Wed Aug 29, 2018 09:05 PM UTC Owner: nobody the issue still occurs. Is it possible...

I'm very pleased to know it has helped you :) Steve On Thu, 30 Aug 2018 at 07:05, Dave Wilbur dvwilbur@users.sourceforge.net wrote: Thank you guys for this thread. I just got an upgraded machine at work and started to get this error after installing the latest Eclipse/EPIC. I have found that either binmode($DB::OUT, ':raw'); or binmode($DB::OUT, ':encoding(UTF-8)'); on line 123 of the new dumpvarepic.pm http://dumpvarepic.pm avoid the fatal warning while using the variables debug window to watch...

Again, thank you Jan. I have the (experimental) debugger console enabled....now I know which checkbox turned it on! Thanks. I figured perl.exe was executing .pl/.pm...I didn't realise that 'dumpvar_epic.pm' was 'compiled' into the org.epic.debug_x.y.z.jar. I have dumpvar_epic.pm open in Notepad++ and I noticed just now as I was debugging my script that it reloaded after being changed on disk, but it is not my copy that changed....it is the normal copy under the ./org.epic.debug/...folder. So, it...

I think I fixed it, but I need someone who understands to verify it.... The second thread above (perl.org) documents the discussion and implementation of the exception we are seeing in the EPIC debugger (below). BTW, looking more closely at the exception message: --- BEGIN --- recv() is deprecated on :utf8 handles. This will be a fatal error in Perl 5.30 a t C:/Perl64/lib/IO/Socket.pm line 304. at C:/Perl64/lib/IO/Socket.pm line 304. IO::Socket::recv(IO::Socket::INET=GLOB(0x323f250), "", 2048) called...

I just found these two link - I consider these authoritative. Could this lead us to the answer? From the Perly Gates: http://www.perlmonks.org/?node_id=1195588 And Mr Ed ('The Horse'): https://rt.perl.org/Public/Bug/Display.html?id=125760 (...forgive me if those references are too obtuse :) )

Hi Jan, First, thank you for the work you have done. I appreciate it. I have this problem too. I tried your suggestion above - created a copy of the two files in another folder which I added to the EPIC path list. It doesn't seem to use my copies. I amnot sure which process/exe actually calls the dumpvar_epic.pm module - perl.exe or the org.eclipse..jar file? I looked at the change you made to the source, read up what I could about the "binmode" command, "Perl::IO" encode, and the utf8 issue. Before...