>> make install should be done with DEBUG_FLAGS containing -g too, otherwise
>> strip(1) is called on the installed binary.
>
>Doh, yes.
I did not do this; that's likely my problem. Thanks.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freeb
>I bet ntpd doesn't call select() in all that many places. Instead of going to
>all this trouble to build a debugging libc, you could just
>grep for select() and place breakpoints on all occurrences. (It might also be
>obvious from looking at them which one is the offender.)
I just checked--th
On Wednesday 24 February 2010 5:09:47 pm Kostik Belousov wrote:
> On Wed, Feb 24, 2010 at 03:17:25PM -0500, John Baldwin wrote:
> > On Wednesday 24 February 2010 1:17:50 pm Peter Steele wrote:
> > > >You're going to need a debug version of libc, too. gdb won't be able to
> > find a backtrace out
On Mon, 22 Feb 2010, Peter Steele wrote:
Just out of curiosity, can you attach to the process via gdb and get a
backtrace? This smells like a locked pthread_join I hit in my own code
a few weeks ago
I'm not using the debug version of ntpd so the backtrace isn't too
useful, but here's what I
On Wed, Feb 24, 2010 at 03:17:25PM -0500, John Baldwin wrote:
> On Wednesday 24 February 2010 1:17:50 pm Peter Steele wrote:
> > >You're going to need a debug version of libc, too. gdb won't be able to
> find a backtrace out of a libc function without it.
> >
> > What's the proper way to build a
>> How do I get libc built with full debug symbols?
>
>I haven't tried it by myself but think here is the way to go: put the
>following to /etc/make.conf and recompile needed libraries / ports.
>WITH_DEBUG=yes
>DEBUG_FLAGS=-g
That didn't seem to have any effect. I still see -O2 being used instea
>> What's the proper way to build a debug version of libc and the other
>> libraries? I tried this:
>
>You can just do this:
>
>cd /usr/src/lib/libc
>make clean
>make DEBUG_FLAGS=-g
>make install
When I tried this the make actually failed with various errors. So I decided to
do a full "make buil
On Wednesday 24 February 2010 1:17:50 pm Peter Steele wrote:
> >You're going to need a debug version of libc, too. gdb won't be able to
find a backtrace out of a libc function without it.
>
> What's the proper way to build a debug version of libc and the other
libraries? I tried this:
You can
--- Begin Message ---
I have home dir's nfs mounted via amd on the jack the following error
occurred on (I do not have NIS I do uid/gid syncing manually):
~/master.C091 ar...@kate% telnet jack
Trying 72.89.191.146...
Connected to jack.istudentunion.com.
Escape character is '^]'.
Trying SRA sec
Andrey Zonov writes:
> Dag-Erling Smørgrav writes:
> > Pointers have no boundareis in C.
> And how free() finds that the need to release?
That is a very simple question with a very complicated answer. Whole
books have been written about the subject. Normally, I'd say "look it
up on Wikipedia",
And how free() finds that the need to release?
Dag-Erling Smørgrav пишет:
Andrey Zonov writes:
When I try allocated pointer to a pointer, and in it some pointers
(important: size is 2 bytes), the pointers lose their boundaries.
Pointers have no boundareis in C.
PS in freebsd < 7
On Wed, Feb 24, 2010 at 12:17:50PM -0600, Peter Steele wrote:
> >You're going to need a debug version of libc, too.
> >gdb won't be able to find a backtrace out of a libc function without it.
>
> What's the proper way to build a debug version of libc and the other
> libraries? I tried this:
>
> e
>You're going to need a debug version of libc, too. gdb won't be able to find
>a backtrace out of a libc function without it.
What's the proper way to build a debug version of libc and the other libraries?
I tried this:
export CFLAGS="-O0"
make buildworld
make installworld DESTDIR=/mydir
and
On Wed, Feb 24, 2010 at 09:43:20AM -0500, John Baldwin wrote:
> On Wednesday 24 February 2010 6:41:31 am Jacques Fourie wrote:
> > I've noticed that my virtualbox vboxdrv.ko started crashing after
> > updating my 8.0-stable install. The crash occurs when vboxdrv calls
> > vtophys() on a userland vi
Andrey Zonov writes:
> When I try allocated pointer to a pointer, and in it some pointers
> (important: size is 2 bytes), the pointers lose their boundaries.
Pointers have no boundareis in C.
> PS in freebsd < 7, it's ok, in Linux too.
Only by accident.
DES
--
Dag-Erling Smørgrav - d...@des.n
On Wednesday 24 February 2010 6:41:31 am Jacques Fourie wrote:
> I've noticed that my virtualbox vboxdrv.ko started crashing after
> updating my 8.0-stable install. The crash occurs when vboxdrv calls
> vtophys() on a userland virtual address. Prior to r202894 this was
> working fine. Modifying pma
On Wed, Feb 24, 2010 at 12:41 PM, Jacques Fourie
wrote:
> I've noticed that my virtualbox vboxdrv.ko started crashing after
> updating my 8.0-stable install. The crash occurs when vboxdrv calls
> vtophys() on a userland virtual address. Prior to r202894 this was
> working fine. Modifying pmap_kext
On Wednesday 24 February 2010 14:44:35 Andrey Zonov wrote:
> Hi,
>
> When I try allocated pointer to a pointer, and in it some pointers
> (important: size is 2 bytes), the pointers lose their boundaries.
> Why it can happen?
>
> Test program in attach.
Your test program is broken:
>#define S1 "
Hi,
When I try allocated pointer to a pointer, and in it some pointers
(important: size is 2 bytes), the pointers lose their boundaries.
Why it can happen?
Test program in attach.
PS in freebsd < 7, it's ok, in Linux too.
--
Andrey Zonov
alloc.c
Description: Binary data
_
On Wed, 24 Feb 2010 13:41:31 +0200
Jacques Fourie wrote:
> I've noticed that my virtualbox vboxdrv.ko started crashing after
> updating my 8.0-stable install. The crash occurs when vboxdrv calls
> vtophys() on a userland virtual address. Prior to r202894 this was
> working fine. Modifying pmap_ke
I've noticed that my virtualbox vboxdrv.ko started crashing after
updating my 8.0-stable install. The crash occurs when vboxdrv calls
vtophys() on a userland virtual address. Prior to r202894 this was
working fine. Modifying pmap_kextract() to use vtopte() for non-kernel
virtual adresses fixes the
21 matches
Mail list logo
