Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • dailybuild_linux-x64
  • dailybuild_win32
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • new_user_dat
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
40 results

sbbs

  • Clone with SSH
  • Clone with HTTPS
  • Rob Swindell (on Windows 11)'s avatar
    Rob Swindell authored
    sbbs_t::gettimeleft() was storing a pointer to a stack (temporary/local)
    variable containing a copy of the next exclusive event cfg (including its
    internal code). This variable, including the internal code, is invalid when
    it goes out of scope. This change makes the sbbs_t::event_code point to the
    sbbs_t::cfg.event[]->code (on the heap) instead.
    
    The only use of this event_code (outside of the event_thread), appears to be
    in the JS bbs.event_code property string. So this fixes issue #705. No other
    observed side effect from this bug.
    
    Constified getnexteventtime() while here. No functional impact.
    1ea66f5b
    History
    Name Last commit Last update