Max Laier wrote:
On Tuesday 18 May 2004 03:57, Tim Kientzle wrote:
<...>
An ideal test archive would not be too big (< 16k) and
have as many as possible of the following:
* regular file
* directory
* hardlink
* symlink
* fifo, socket, device node, etc.
* regular file with very long path
On Tuesday 18 May 2004 03:57, Tim Kientzle wrote:
<...>
> An ideal test archive would not be too big (< 16k) and
> have as many as possible of the following:
>* regular file
>* directory
>* hardlink
>* symlink
>* fifo, socket, device node, etc.
>* regular file with very long
In order to test bsdtar's automatic format detection and
support for variant tar formats, I'm looking for sample
archives generated by a variety of tar programs.
In particular, I'm looking for tar archives generated by:
* Very old versions of tar (pre-1980 is especially
interesting)
* Vario
On Mon, May 17, 2004 at 03:17:03PM -0700, Marcel Moolenaar wrote:
> On Mon, May 17, 2004 at 10:45:39PM +0200, Mark Kettenis wrote:
> >
> >I cannot prevent you from committing this, but if it doesn't address
> >the items mentioned above, it may not be used on FreeBSD. Unless I'm
> >bei
On Sat, May 15, 2004 at 01:00:13PM +0200, Cyrille Lefevre wrote:
> "Yar Tikhiy" <[EMAIL PROTECTED]> wrote:
> [snip]
> > Considering all the above, I'd like to add the following paragraph
> > to the flock(2), lockf(3), and fcntl(2) man pages (replacing the
> > sentence quoted from lockf(3)):
> >
>
On Mon, May 17, 2004 at 10:45:39PM +0200, Mark Kettenis wrote:
>
>I cannot prevent you from committing this, but if it doesn't address
>the items mentioned above, it may not be used on FreeBSD. Unless I'm
>being relieved of gdb duties of course :-)
>
> Let's see. My kvm stuff would
On Mon, May 17, 2004 at 01:32:00PM +0200, Mark Kettenis wrote:
> I've recently implemented support for kvm(3)-based debugging that
> works for all three BSD's. The interface is fairly simple, just start
> GDB on a kernel binary, i.e.
*snip*
> All that's needed is a bit of new code (bsd-kvm.[ch])
В Пнд, 17.05.2004, в 16:04, Kevin A. Pieckiel пишет:
> On Fri, May 14, 2004 at 11:33:49AM -0400, John Baldwin wrote:
>
> > Do 'l *0xc0519a64' in gdb to get the line that it actually faulted on. Since
> > this is likely a NULL pointer deref that might help you fix the bug or at
> > least find ou
On Fri, May 14, 2004 at 11:33:49AM -0400, John Baldwin wrote:
> Do 'l *0xc0519a64' in gdb to get the line that it actually faulted on. Since
> this is likely a NULL pointer deref that might help you fix the bug or at
> least find out its cause.
Wow. That's interesting to me. I didn't expect
FreeBSD, NetBSD and OpenBSD all provide the kvm(3) interface for
debugging kernel virtual memory images: kernel crash dumps and live
kernels. All three include support for this interface in the version
of GDB bundled with the OS, but this code was never contributed back.
I've recently implemented
10 matches
Mail list logo
