From: Eric Wong <email@example.com> To: vtamara <firstname.lastname@example.org> Cc: Jeremy Evans <email@example.com>, firstname.lastname@example.org Subject: Re: Bus Error with Unicorn 6.0 on OpenBSD/adJ 6.8 with Ruby 3.0 Date: Sun, 4 Apr 2021 20:03:58 +0000 [thread overview] Message-ID: <20210404200358.GA32719@dcvr> (raw) In-Reply-To: <YGnsxfqRYQFzA3email@example.com> Jeremy Evans <firstname.lastname@example.org> wrote: > Unfortunately, given the required amount of setup, I don't think I'll > have time to look into this. The best way to debug this is to start > removing code/dependencies piece by piece until the problem goes away. > Once the problem goes away, add that code back, and make sure it fails > again, then start removing other code/dependencies. Repeat this process > until you have the most minimal example, where removing any additional > code/dependencies will stop the code from failing. The above is exactly what I would do, too. I would also try to correlate the time of Bus Errors with logs of when + which requests are failing, and try replaying only those requests to narrow things down. Also, do you have core dumps enabled? Enable those ("ulimit -c unlimited" in sh), and run gdb on them as you get them. The .gdbinit in the source tree of the Ruby version you're using is helpful not just for Ruby itself, but also C extensions, too. I'm no a gdb expert, but it's well-documented and has built-in help.
next prev parent reply other threads:[~2021-04-04 20:03 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-29 19:06 vtamara 2021-03-30 1:58 ` Eric Wong 2021-03-30 4:00 ` Jeremy Evans 2021-04-04 11:06 ` vtamara 2021-04-04 16:43 ` Jeremy Evans 2021-04-04 20:03 ` Eric Wong [this message] 2021-04-07 21:19 ` Bus Error with Unicorn 6.0 on OpenBSD-current (6.9) with Ruby 3.0 in minimal rails application vtamara 2021-04-08 2:11 ` Jeremy Evans 2021-04-12 22:47 ` vtamara
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://yhbt.net/unicorn/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210404200358.GA32719@dcvr \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Bus Error with Unicorn 6.0 on OpenBSD/adJ 6.8 with Ruby 3.0' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: ../../unicorn.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).