Opened 3 years ago

Closed 2 years ago

#1343 closed defect (not relevant)

Padre seg faults when syntax checking some 'use' statements

Reported by: gyles19 Owned by:
Priority: major Milestone:
Component: not classified yet Version: 0.90
Keywords: Cc:

Description

Padre will seg fault and dump core when asked to syntax check a short perl script which attempts to 'use' a module which has a BEGIN block in it, where that BEGIN block makes assumptions the script doesn't (yet) meet. Padre appears to hang (but it's writing a huge 200+meg core file) and then dies.

See attached files for details.

Attachments (4)

padre.log (852 bytes) - added by gyles19 3 years ago.
Log of padre invocation and the error it prints to stdout
padre.core.backtrace.txt (12.1 KB) - added by gyles19 3 years ago.
gdb back trace of perl & all the threads
die_padre_die.pl (304 bytes) - added by gyles19 3 years ago.
The padre killer itself
perl_bt.txt (1.2 KB) - added by gyles19 3 years ago.
Perl back trace of the seg fault

Download all attachments as: .zip

Change History (7)

Changed 3 years ago by gyles19

Log of padre invocation and the error it prints to stdout

Changed 3 years ago by gyles19

gdb back trace of perl & all the threads

Changed 3 years ago by gyles19

The padre killer itself

Changed 3 years ago by gyles19

Perl back trace of the seg fault

comment:1 Changed 3 years ago by azawawi

with r16861, we now have syntax checking on/off pragmas. Does that help?

comment:2 Changed 3 years ago by gyles19

That should be a reasonable work-around for the underlying issue. The problem will be, how will an end-user like me be able to recognize why Padre crashed in the first place? Editors shouldn't be so picky as to suicide when the user types a syntax error, much less when the line involved has no obvious syntax errors.

For me, I prefer the vim approach...make a good stab at the coloring, but don't sweat the occasional error. It's much more important to not lose unsaved work in progress, than it is to have every shade of pink exactly right... We all understand perl is a nightmare to parse. Padre's stability is much more important than pretty source code.

comment:3 Changed 2 years ago by bowtie

  • Resolution set to not relevant
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.