Re: GDB & Linux binaries.

2002-11-10 Thread soralx
> > I'm guessing this is because the linux libc library file is in > > /usr/compat/linux/lib, how do I get GDB to use it instead? Or is it even > > possible. That's interesting. I already asked similar question here, on freebsd-hackers@, but was immediately sent to freebsd-questions@, where I didn

Re: GDB & Linux binaries.

2002-11-10 Thread Daniel O'Connor
On Mon, 2002-11-11 at 05:38, Ryan Sommers wrote: > I'm guessing this is because the linux libc library file is in > /usr/compat/linux/lib, how do I get GDB to use it instead? Or is it even > possible. I believe you can install the linux_devtools* port and get gdb for Linux. There is also linux_kd

vmstat to detect memory leaks?

2002-11-10 Thread Chuck Tuffli
I'm developing a loadable module and was wondering if I can use the output of vmstat to figure out if there is memory leak over the course of some testing. For example, #!/bin/sh vmstat > before kldload mymodule.ko ./run_tests.sh kldunload mymodule vmstat > after ./compare_free.sh before after Tn

Re: stack alignment, XEON / P4

2002-11-10 Thread David Schultz
Thus spake Don Bowman <[EMAIL PROTECTED]>: > In sys/conf/kern.mk, there is a comment about not aligning > the (x86) stack to 16-byte boundaries, and it overrides the > preferred-stack-boundary to 2. > > .if ${MACHINE_ARCH} == "i386" > CFLAGS+=-mno-align-long-strings -mpreferred-stack-boun

stack alignment, XEON / P4

2002-11-10 Thread Don Bowman
In sys/conf/kern.mk, there is a comment about not aligning the (x86) stack to 16-byte boundaries, and it overrides the preferred-stack-boundary to 2. .if ${MACHINE_ARCH} == "i386" CFLAGS+=-mno-align-long-strings -mpreferred-stack-boundary=2 .endif This seems to be contradicted by intel's

GDB & Linux binaries.

2002-11-10 Thread Ryan Sommers
Is it possible to use GDB on linux binaries? When I try to run the program in GDB I get the following errors: (gdb) run Starting program: /usr/home/ryans/src/bomb/bomb warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track expl

Re: Filesystem corruption

2002-11-10 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Nick Rogness w rites: >> The fix is to not run dump(8) on a live filesystem. You should >> either use a snapshot or umount the device. > > I've been running dump for years on live filesystems with FreeBSD > and never had a problem. I was not aware of a

Re: Filesystem corruption

2002-11-10 Thread David Schultz
Thus spake Nick Rogness <[EMAIL PROTECTED]>: > I've been running dump for years on live filesystems with FreeBSD > and never had a problem. I was not aware of any snapshot feature > available for 4.X-STABLE (only 5.0)? > > umounting a live filesystem to back it up is not a

Re: Filesystem corruption

2002-11-10 Thread Nick Rogness
On Sat, 9 Nov 2002, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Larry Sica wri > tes: > >-BEGIN PGP SIGNED MESSAGE- > >Hash: SHA1 > > > >Not sure if hackers is the correct place to ask about this but... > > > >On Friday, November 8, 2002, at 06:28 PM, Nick Rogness wrote: > >