I was able to build a copy of the libgl1-mesa-dri with the Gallium i915
driver enabled, and that fixed the flickering problem on my netbook from
that era.
Here's a copy if anyone would like to try
https://github.com/wh0/debian-mesa-i915g/releases/tag/22.3.0-1-1
I saw that Fedora had enabled it
I tried it, just modifying /usr/sbin/ddclient. It works now.
I don't have any Perl programming experience; there's got to be a more
idiomatic way than initializing it to 0 and then conditionally assigning 1.
On Thu, Jul 28, 2016, 8:41 PM Torsten Landschoff
wrote:
> Hi,
(can't see my previous message. resending.)
#0 0x in ?? ()
#1 0xb7be786c in execute_helper (master_fd=master_fd@entry=5,
argv=argv@entry=0xbfffebbc) at iface.c:110
#2 0xb7be79d3 in utempter_add_record (master_fd=5, hostname=0xb28c
"mosh [3749]") at iface.c:146
#3 0x80006d59 in
I have the same problem. I found that in dmesg, there were several lines
about mosh-server crashing by segfault, for example:
[ 2980.423340] mosh-server[7104]: segfault at 0 ip (null) sp bfd4bb6c error
14 in mosh-server[80001000+58000]
Here's some info from running mosh-server in GDB. I don't
update:
turns out you actually have to turn on the fixup trap
$ echo 2 | sudo tee /proc/cpu/alignment
3
$ jsc
'-ab'.match(/ab/)
ab
https://wiki.debian.org/ArmEabiFixes#word_accesses_must_be_aligned_to_a_multiple_of_their_size
Though this wiki page recommends, you cannot rely on this being
This has been hard, because for some reason, in remote debugging, I can't
step or continue once I've hit a breakpoint. Anyway, I've gotten through to
the suspicious behavior by stepping through the assembly on the device. The
weird stuff happens in YARR-generated code, so there's no symbols there
Here's a disassembly of the pattern /AT\W/i.
http://paste.debian.net/98876/
High level overview: a loop starts at 0xb390a038. r0 is a pointer to the
string, and r1 is the current search index plus 3.
- it does a halfword load, converts it to lowercase, and checks it against
at
- if it's not
I made progress on getting gdb to work. It turns out I was loading the
symbol file wrong, causing gdb to map it to the wrong address, which
explains the Cannot access memory at messages. I'll try to step through
starting at JSC::stringProtoFuncMatch to see what happens.
No real findings so far.
that's causing a problem.
No real findings so far.
On Fri, May 9, 2014 at 3:55 AM, Alberto Garcia be...@igalia.com wrote:
On Thu, May 08, 2014 at 12:08:40PM -0700, wh wrote:
welp, I'd better try debugging it or something.
We would appreciate if you can keep us up-to-date with your findings
welp, I'd better try debugging it or something.
Thanks for trying it out.
On Thu, May 8, 2014 at 6:15 AM, Alberto Garcia be...@igalia.com wrote:
On Mon, May 05, 2014 at 05:57:04AM +, microrffr+debian@gmail.comwrote:
In jsc from libjavascriptcoregtk-3.0-bin:
Package: python-apt
Version: 0.9.1
in doc/source/library/apt_pkg.rst, lines 718, 726, 736 have different
indentation from the other attributes.
rendition:
http://apt.alioth.debian.org/python-apt-doc/library/apt_pkg.html#apt_pkg.Package
11 matches
Mail list logo