g can be avoided altogether.
Attached patch (also available as
https://github.com/emaste/diffoscope/commit/e709c11212a18105f3b6862d5ed20de61038b71a)
is my approach at addressing this.
commit e709c11212a18105f3b6862d5ed20de61038b71a
Author: Ed Maste
Date: Tue Feb 14 16:42:20 2017 -0500
Fixed upstream in FreeBSD r302398
https://svnweb.freebsd.org/changeset/base/302398
Thanks for the report -- I will fix this upstream.
Package: diffoscope
Version: 54
Severity: wishlist
I am using diffoscope on FreeBSD and often encounter very long run
times. I've since found that the same issue is known upstream: a
number of Debian reproducibility bugs are tagged with
diffoscope_runs_forever[1] and the Debian CI infrastructure k
On 30 June 2015 at 17:17, Steven Chamberlain wrote:
> Hi!
>
> So I think we may want to build kfreebsd-10 using clang-3.6, to keep
> consistency with kfreebsd-11, and so that we rely on fewer clang
> releases to be maintained simultaneously in Debian.
Note that upstream FreeBSD 11 will soon switc
On 20 August 2014 15:56, Steven Chamberlain wrote:
> Hi,
>
> I've tested for this vt(4) issue in upstream's own kernel build from:
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/10.0-STABLE
> and it is affected as well. It is only a problem when using Qemu with
> the "-enable-kvm" option (an
> On 22/07/14 19:58, Jan Henke wrote:
>> I am experiencing a strange problem with the current kFreeBSD weekly
>> image. Whenever the system is writing to the screen in text mode (e.g.
>> directly after selecting one entry in GRUB: "Copyright") you can
>> literally watch every single character p
On 4 March 2014 01:54, Vagrant Cascadian wrote:
> Control: severity 730833 important
>
> On Tue, Feb 18, 2014 at 11:19:29PM +, Robert Millan wrote:
>> On 18/02/2014 21:54, Vagrant Cascadian wrote:
>> > On Tue, Feb 18, 2014 at 09:35:09PM +, Robert Millan wrote:
>> >> On 18/02/2014 19:11, Va
On 12 February 2014 09:05, Robert Millan wrote:
> There's a small glitch during VT switch: immediately after pressing the
> keys, screen is redrawn, but where you'd normally see the login prompt,
> blurry characers are drawn. After a fraction of a second, these are replaced
> with proper glyphs. S
On 8 February 2014 08:49, Robert Millan wrote:
> Package: kfreebsd-image-11.0-0-amd64
> Version: 11.0~svn260666-1
> Severity: important
>
> With Newcons it becomes practically impossible to use the console. When
> using the default VESA driver, both VT switching and text scrolling
> become terribl
> osgearth also knows how to use Windows and Mac OS X--specific syscalls
> to get a thread ID. This is not portable and there is nothing directly
> equivalent on FreeBSD, see:
> http://lists.freebsd.org/pipermail/freebsd-hackers/2010-June/031992.html
The FreeBSD equivalent is:
int pthread_getthre
This is fixed in stable/9 in r255443. The offending commit was already
reverted from the 9.2 branch prior to 9.2-RC3 for other reasons.
On 10 September 2013 07:31, Steven Chamberlain wrote:
> Package: src:kfreebsd-9
> Version: 9.2~svn253912-1
> Severity: grave
> Tags: security upstream
>
> ht
For now at least, the message can just be ignored.
Unfortunately there's no clean way to address it - the thread at
http://lists.freebsd.org/pipermail/svn-src-all/2013-May/068590.html
has some of the context.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject o
On Mon, Jun 13, 2011 at 09:11:41AM +0200, Lennart Poettering wrote:
> Nah, I will not work on this. Netlink is Linux specific -- it cannot be
> made on the legacy kernels, and I don't care for the legacy kernels
> anyway and won't spend time on them.
At the BSDCan conference last month we had som
On Mon, Sep 13, 2010 at 10:55:54PM +0200, Tuco wrote:
> Btw FreeBSD handbook
> (http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN)
> says dumpon and savecore are needed to save and restore crash dumps so
> I ported them and added them to freebsd-utils in c
On Mon, Sep 13, 2010 at 02:50:25PM +0200, Petr Salinger wrote:
> fails (panic in swapper) similarly also for me.
Can you add the following options to the kernel config and recompile,
to help track down the problem:
# Compile with kernel debugger related code.
options KDB
# Print a stac
16 matches
Mail list logo
