Keyboard input in Javascript file causes seg fault

Bug #990716 reported by Ben Linsey-Bloom
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bluefish
Fix Released
High
bluefish (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Running Bluefish 2.2.2 on Ubuntu 12.04 64-bit.

To recreate the Bluefish crash:
1. Create new file

2 . Paste in this line:
tagCloud.innerHTML += '&nbsp\; <a href="javascript:tagClick();" style="font-size: ' + tags[i].size + '%\;">' + tags[i].id + '</a> &nbsp\;';

3. Save as a Javascript file (choose any file name with '.js' extension). Bluefish applies Javascript colours to the code.

4. In the code, locate 'tagClick()' and quickly try to put two single quotes (the ' symbol ) in the parenthesis '()' so 'tagClick()' becomes 'tagClick('')'.

If you type slowly it might be okay, but if you type the single quotes quickly, bluefish crashes on my machine every time.

Run from the terminal I get this result:

ben@mr-shinyface:~$ bluefish
Language statistics for Javascript from /usr/share/bluefish/bflang//javascript.bflang2
reference size 0.02 Kbytes
largest table 2706 ( 676.50 Kbytes)
total tables 2748 ( 687.00 Kbytes)
contexts 10 ( 0.47 Kbytes)
matches 531 ( 37.34 Kbytes)
Segmentation fault (core dumped)
ben@mr-shinyface:~$

I'll keep trying to narrow it down and see exactly which part of this code is causing the problem. Please get back to me if you need more info.

Revision history for this message
Ben Linsey-Bloom (ben-kitserve) wrote :

I've found that disabling Document > Highlight Syntax stops the bug from occuring.

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

Please install bluefish-dbg and gdb. Then run `gdb' and inside the debugger session type `set logging on' and `r bluefish'. Reproduce the segmentation fault. When the program stops and gdb reports the error, then type `bt full', then quit and attach the gdb.txt file to this report. See also

http://bfwiki.tellefsen.net/index.php/Debugging_Bluefish#Run_Bluefish_in_the_debugger.

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

I created a backtrace and opened a report in the upstream bug-tracker. You don't need to do it.

Changed in bluefish:
importance: Unknown → High
status: Unknown → Confirmed
Revision history for this message
Ben Linsey-Bloom (ben-kitserve) wrote :

Awesome thanks for the speedy response.

Changed in bluefish:
status: Confirmed → In Progress
Changed in bluefish:
status: In Progress → Fix Released
Vibhav Pant (vibhavp)
Changed in bluefish (Ubuntu):
assignee: nobody → Vibhav Pant (vibhavp)
Vibhav Pant (vibhavp)
Changed in bluefish (Ubuntu):
assignee: Vibhav Pant (vibhavp) → nobody
Changed in bluefish (Ubuntu):
status: New → In Progress
Changed in bluefish (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

via 2.2.3-1

Changed in bluefish (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.