From: "evvers at ya dot ru" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/28659] UBSan seems to complain about an "integer overflow" in dwfl_segment_report_module
Date: Thu, 09 Dec 2021 20:24:22 +0000 [thread overview]
Message-ID: <bug-28659-10460-wuN9EF0Wjo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28659-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28659
--- Comment #4 from Evgeny Vereshchagin <evvers at ya dot ru> ---
> But it comes with a horribly proprietary license
Unfortunately LGTM (like many other CI services) is tightly coupled with GitHub
(where it can be used for automated analysis of open source projects) so in
theory it should be possible to keep a read-only fork of the elfutils
repository updated by a cron script run by buildbot. I'm not sure whether it's
worth it though.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-12-09 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 13:01 [Bug libdw/28659] New: " evvers at ya dot ru
2021-12-08 21:43 ` [Bug libdw/28659] " mark at klomp dot org
2021-12-08 22:39 ` evvers at ya dot ru
2021-12-09 19:30 ` mark at klomp dot org
2021-12-09 20:24 ` evvers at ya dot ru [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-28659-10460-wuN9EF0Wjo@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).