You are here


Shebanging a SmallBASIC script under Ubuntu?

SmallBASIC implementations: 

Hi all,

These days I tried playing with SB and making a simple script executable directly from the command line. As advertised in the sourceforce SB guide, chapter 1.4.1, I made my script executable and tried

#!/usr/bin/sbasic -q

as a shebang line, but when trying to run it, I got a "file not found" message (referring to the interpreter, not to the source). This is fair enough, because after the installation, there is no "sbasic" file in the /usr/bin folder. There actually *is* a file "sbasici", but if I change the shebang to:


FLTK version release history

SmallBASIC implementations: 

0.11.16 Thursday, 2/10/2014

  • Release for 32 bit linux. This release includes language and performance improvements. See release notes page.

0.11.11 Sat, 26/07/2014

  • Release for 64 bit linux. This is mostly the same as the Windows version.

0.11.5 Sun, 20/04/2014

Segmentation fault on editor font size change unless program has been run

SmallBASIC implementations: 

Consider the difference between the following two tasks:

Font indexer segmentation fault if open() returns EACESS (not actually major)

SmallBASIC implementations: 

  open("/250gb/usr/share/fonts/artwiz-fonts/gelly.pcf", O_RDONLY) = 5
  fcntl64(5, F_SETFD, FD_CLOEXEC) = 0
  fstat64(5, {st_mode=S_IFREG|0644, st_size=5768, ...}) = 0
  mmap2(NULL, 5768, PROT_READ, MAP_PRIVATE, 5, 0) = 0xb6b3e000
  close(5) = 0
  munmap(0xb6b47000, 30760) = 0
  open("/250gb/usr/share/fonts/artwiz-fonts/", O_RDONLY) = 5
  fcntl64(5, F_SETFD, FD_CLOEXEC) = 0

Background font scanning using 100% CPU

SmallBASIC implementations: 

Hi everyone :)

I recently discovered SmallBASIC, and last night I downloaded and compiled it (on Linux, using FLTK)... only to discover, after firing it up, that it was using 100% CPU with just a blank editor window open.

"Huh. Hopefully I can fix that tomorrow, SmallBASIC looks pretty cool..."

Well, I ran it through strace today, to discover it was chowing its way through my font directories. ("...?!")

After further poking it with gdb I found that this was actually... part of the design.

Oh. That's kind've a problem.


Subscribe to RSS - Linux