Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Padre segfaults when Padre::Plugin::Snippet is enabled #7

Open
marderh opened this issue Oct 19, 2014 · 7 comments
Open

Padre segfaults when Padre::Plugin::Snippet is enabled #7

marderh opened this issue Oct 19, 2014 · 7 comments

Comments

@marderh
Copy link

marderh commented Oct 19, 2014

When i enable Padre::Plugin::Snippet via Plug-in-Manager in Padre, either Padre crashes instantly with a segfault. After a restart it starts, but at the first serious action (opening a file, Help->Report a new Bug) Padre crashes again. When the said module is disabled everything works as expected
again.

OS: Linux, Debian Jessie (testing)
Padre: 1.00 (1.00+dfsg-3) installed from .deb
Padre::Plugin::Snippet: 0.01-2 installed from .deb

@marderh
Copy link
Author

marderh commented Oct 19, 2014

Just noticed Padre crashes with Help->Report a new Bug, independently from the plugin-settings.

@kevindawson
Copy link
Member

marderh hi

i have just tested padre dev from github with Padre::Plugin::Snippet

it dose not segfault

there are how ever some wxWidget issues, sad

have you viewed -> http://padre.perlide.org/trac/wiki/PadrePluginSnippet

Snippet mode can be entered through works as per wiki :)

azawawi any thoughts

@marderh
Copy link
Author

marderh commented Oct 19, 2014

I suppose it has something to do with the wx-issues you mentioned. Sometimes it just crashes when opening a File from Project Browser:
Prototype mismatch: sub Wx::Event::EVT_GRID_CELL_CHANGE: none vs ($$) at /usr/lib/x86_64-linux-gnu/perl5/5.20/Wx/Grid.pm line 67. Prototype mismatch: sub Wx::Event::EVT_GRID_CMD_CELL_CHANGE: none vs ($$$) at /usr/lib/x86_64-linux-gnu/perl5/5.20/Wx/Grid.pm line 68. No such file or directory when trying to open 'script.pl' at /usr/share/perl5/Padre/Wx/Main.pm line 4123. variable is not of type Wx::TreeItemId at /usr/share/perl5/Padre/Wx/Directory/TreeCtrl.pm line 115. Perl exited with active threads: 5 running and unjoined 0 finished and unjoined 0 running and detached

@kevindawson
Copy link
Member

mardeth

do a git clone of padre
then perl Makefile.PL
install dependancies
then make
and then perl dev to launch

that way we will both be using the same current version of padre

@marderh
Copy link
Author

marderh commented Oct 20, 2014

Ok. Did that on another workstation (also with Debian Jessie) and get the same issue:
Enable Plugin -> Restart -> Open File -> pooof

@nxadm
Copy link
Contributor

nxadm commented Oct 20, 2014

I installed Padre and Padre::Plugin::Snippet on a newly installed Jessy (beta 2) 32-bit VM and I don't get the application to crash. However, once I installed the Virtualbox guest additions (including video drivers), it did crash:
"padre: Fatal IO error 11 (Resource temporarily unaavailable) on X server :0."

@marderh
Copy link
Author

marderh commented Oct 21, 2014

Maybe this helps to reproduce the error somewhere:

Help -> About -> Information
From the debian-packet:

Padre 1.00 Core... osname linux archname x86_64-linux-gnu-thread-multi Distribution Debian GNU/Linux jessie/sid Kernel 3.16-2-amd64 Perl 5.20.1 Threads 8 RAM 1686.8MB Wx... Wx 0.9923 WxWidgets 3.0.1 unicode 1 Alien::wxWidgets 0.65 Wx::Perl::ProcessStream 0.32 Wx::Scintilla 0.39 Other... PPI 1.218 Debug::Client 0.29 PPIx::EditorTools 0.18 Config /home/sk/.local/share/.padre

and from the git clone:

Padre 1.01 Core... osname linux archname x86_64-linux-gnu-thread-multi Distribution Debian GNU/Linux jessie/sid Kernel 3.16-2-amd64 Perl 5.20.1 Threads 3 RAM 532.0MB Wx... Wx 0.9923 WxWidgets 3.0.1 unicode 1 Alien::wxWidgets 0.65 Wx::Perl::ProcessStream 0.32 Wx::Scintilla 0.39 Other... PPI 1.218 Debug::Client 0.29 PPIx::EditorTools 0.18 Config /home/sk/devel/Padre/.padre

Best regargs,
m

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants