Subhashish Pradhan, le Sat 13 Sep 2014 14:58:04 +0530, a écrit :
> So may I re-base my work on the new Valgrind 3.10.0? Comments please.
I'd say so, yes: better catch up early than late (but not in the
development branch, where it may be a mess at times).
Samuel
Thomas Schwinge, le Tue 16 Sep 2014 00:08:01 +0200, a écrit :
> Do you agree that thread_get_state(i386_DEBUG_STATE) should be
> returning the actual DR6,
Indeed.
> and where in GNU Mach would we need to copy the DR6
> register into the PCB?
it would be user_trap(), probably, in the T_DEBUG case
Hi Samuel!
On Fri, 12 Sep 2014 19:56:13 +0200, I wrote:
> Many thanks for persisting with this patch. The GDB testsuite shows a
> pretty good improvement! I'll try to assess the remaining issues
From a quick scan through the »FAIL:.*watch« matches, the following one
issue should be relevant for
On Thu, Feb 27, 2014 at 10:17:07PM +0100, Richard Braun wrote:
> I intend to regularly update these packages to track the experimental
> branch until the changes are merged in the official repository.
Iceweasel 31.1.0esr-1 (from unstable) is available.
--
Richard Braun
> Seeing a submission to gdb getting stuck on missing line breaks got me
> a bit on my nerves. Fortunately it wasn't only about that, but also
> important changes, so I carried on, but having to resubmit only for
> missing spaces or new lines would have been really hard to me, since I
> don't reall
Quoting Justus Winter (2014-09-12 21:06:30)
> Killing the crash server I managed to get my shutdown process going
> again, though it got stuck again. Using the kernel debugger (at this
> point, sysvinit succesfully killed all my shells) I could see that
> indeed another crash server has been spawn
Hi,
Justus Winter wrote:
The output changes, but hangs in the same place:
<...>
start ext2fs: ext2fs: device:hd0s1: warning: FILESYSTEM NOT UNMOUNTED
CLEANLY; PLEASE fsck
ext2fs: device:hd0s1: warning: MOUNTED READ-ONLY; MUST USE 'fsysopts
''writable'
Hurd server bootstrap: ext2fs[device:hd0s1]
