Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a recommended way to catch errors at startup? #180

Open
iamFIREcracker opened this issue Jan 14, 2023 · 0 comments
Open

Is there a recommended way to catch errors at startup? #180

iamFIREcracker opened this issue Jan 14, 2023 · 0 comments

Comments

@iamFIREcracker
Copy link

iamFIREcracker commented Jan 14, 2023

I would like to catch USOCKET:ADDRESS-IN-USE-ERROR so I can prompt the user to provide a different port, but it looks like the error is getting thrown in a background thread.

Hunchentoot server is started.
Listening on 127.0.0.1:4242.

debugger invoked on a USOCKET:ADDRESS-IN-USE-ERROR in thread
#<THREAD "clack-handler-hunchentoot" RUNNING {7005713283}>:
  Condition USOCKET:ADDRESS-IN-USE-ERROR was signalled.

The current thread is not at the foreground,
SB-THREAD:RELEASE-FOREGROUND has to be called in #<SB-THREAD:THREAD "main thread" waiting on: #<WAITQUEUE clack-handler-hunchentoot {7005713203}> {700546AB13}>
for this thread to enter the debugger.

Happy to look into this, but if you got some hints, please share with me before I get down the rabbit hole!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant