1. 19 May, 2000 3 commits
  2. 18 May, 2000 3 commits
  3. 17 May, 2000 2 commits
  4. 16 May, 2000 4 commits
  5. 15 May, 2000 5 commits
  6. 14 May, 2000 1 commit
  7. 11 May, 2000 1 commit
  8. 08 May, 2000 1 commit
  9. 04 May, 2000 2 commits
  10. 02 May, 2000 6 commits
  11. 01 May, 2000 1 commit
  12. 29 Apr, 2000 1 commit
  13. 27 Apr, 2000 4 commits
  14. 26 Apr, 2000 2 commits
  15. 25 Apr, 2000 1 commit
    • Geoff Thorpe's avatar
      This case in the "dso_unload" handlers should not be reported as an error - · ebbaebf7
      Geoff Thorpe authored
      if a DSO_load(NULL,...) operation fails, it will have to call DSO_free() on
      the DSO structure it created and that will filter through to this "unload"
      call.
      
      If the stack size is "< 1", then the library never actually loaded. To keep
      things clean higher up, I'll treat this as a vacuous case without an error.
      It makes the error stack easier to follow real world cases, and the error
      this ignores was only useful for catching bugs in internal code, not
      mismatched calls from applications (which should be handled in the generic
      DSO layer).
      ebbaebf7
  16. 20 Apr, 2000 2 commits
  17. 19 Apr, 2000 1 commit