Re: Developer Questions (glibc i386 style backtraces)

2007-07-16 Thread Roland Smith
On Sun, Jul 15, 2007 at 07:53:35PM -0400, Michael B Allen wrote:
 Hello Again,
 
 Is there a good list to ask developer questions about porting code to 
 FreeBSD?

-questions, or maybe -hackers if it gets really complicated.

 I have a good chunk of code to port and no doubt I will have numerous
 questions about FreeBSD specific features like semaphores, posix
 compliance, shared memory and so on.

For shared memory, look at /usr/include/sys/shm.h. For semaphores, see
/usr/include/sys/sem.h.

There is a lot of documentation available on the FreeBSD website;
http://www.freebsd.org/docs/books.html 

In your case, the Developers' Handbook might come in handy.

It is also available on the system btw, in /usr/share/doc/en_US.ISO8859-1

 Actually my current issue is the glibc i386 backtrace function from
 execinfo.h. It's not a show stopper if I can't have it but I would
 very much like to have it even if it means writing custom code to walk
 the stack myself.

I think that the glib library has this. It turns up a backtrace.h on my system.
There is no execinfo.h file on my system.
 
 Any ideas? Googling doesn't seem to turn up anything which is to say I
 guess FreeBSD doesn't have a backtrace function.

A quick search of the base system doesn't turn anything up. But
debuggers like gdb work, so there has to be a way to do it.

 Actually does FreeBSD use glibc?

Nope.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpQP9WhHN6DK.pgp
Description: PGP signature


Developer Questions (glibc i386 style backtraces)

2007-07-15 Thread Michael B Allen

Hello Again,

Is there a good list to ask developer questions about porting code to FreeBSD?

I have a good chunk of code to port and no doubt I will have numerous
questions about FreeBSD specific features like semaphores, posix
compliance, shared memory and so on.

Actually my current issue is the glibc i386 backtrace function from
execinfo.h. It's not a show stopper if I can't have it but I would
very much like to have it even if it means writing custom code to walk
the stack myself.

Any ideas? Googling doesn't seem to turn up anything which is to say I
guess FreeBSD doesn't have a backtrace function.

Actually does FreeBSD use glibc?

Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Developer Questions (glibc i386 style backtraces)

2007-07-15 Thread Garrett Cooper

Michael B Allen wrote:

Hello Again,

Is there a good list to ask developer questions about porting code to 
FreeBSD?


I have a good chunk of code to port and no doubt I will have numerous
questions about FreeBSD specific features like semaphores, posix
compliance, shared memory and so on.

Actually my current issue is the glibc i386 backtrace function from
execinfo.h. It's not a show stopper if I can't have it but I would
very much like to have it even if it means writing custom code to walk
the stack myself.

Any ideas? Googling doesn't seem to turn up anything which is to say I
guess FreeBSD doesn't have a backtrace function.

Actually does FreeBSD use glibc?

Mike


FreeBSD is actually based off of libc, which is a completely different 
set of sources from glibc.


I don't have any resources and I don't know right offhand whether or not 
libc has a backtrace function. You may want to ask this on the hackers@ 
list.


Cheers,

-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]