nl_langinfo problem

2006-06-28 Thread Joseph Maxwell
It seems that I am addressing a FreeBSD problem after a Perl installation and a rebuild of the shared lib files Now some perl programs don't work and some apparently non-perl programs have suferred the same faith as well. Its a bit confusing and help is needed !! ___ Sys S

Re: adm1026 support

2006-06-28 Thread YTR
Hi, Can you tell me on which Release of BSD (5.5 or pre 5.5) have the support for ADM1026 Driver? Thanks, YTR -- View this message in context: http://www.nabble.com/adm1026-support-tf1800838.html#a5078824 Sent from the freebsd-hackers forum at Nabble.com. _

Re: adm1026 support

2006-06-28 Thread Gary Jennejohn
YTR writes: > Can you tell me on which Release of BSD (5.5 or pre 5.5) have the support > for ADM1026 Driver? > It isn't supported, but see this: http://lists.freebsd.org/pipermail/freebsd-hackers/2006-June/016886.html --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOT

wine: mapping memory problems

2006-06-28 Thread asgard
hi, all. in wine project there are few problems on freebsd with windows 16-bits programs. when you'll run such program, wine will crashed with stack overflow. in fact, on freebsd wine doesn't map 1st megabyte of virtual memory, but it should. see ./libs/wine/mmap.c ./dlls/winedos/dosmem.c ./libs/

Re: [fbsd] Source ScreenSaver

2006-06-28 Thread Jeremie Le Hen
Hi, > It follows link of the code and the procedures > > http://200.193.29.195/saver/index.html I have just given a try to it and I must admit it is very, very good looking. I even prefer it to the non-OpenGL matrix module from xscreensaver. Is it possible to added it to the source tree, or ar

Return value of malloc(0)

2006-06-28 Thread Andre Albsmeier
There is a nice extension for firefox called prefbar. However, newer versions of prefbar (>=3.3) make firefox die with SIGSEGV, see http://bugzilla.mozdev.org/show_bug.cgi?id=13809 for details. The crash happens in libgklayout.so: Program received signal SIGSEGV, Segmentation fault. [Switching to

RE: nl_langinfo problem

2006-06-28 Thread Joseph Maxwell
Problem Solved perl-freebsd, Anton Berezin _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ _

Re: Return value of malloc(0)

2006-06-28 Thread Lowell Gilbert
Andre Albsmeier <[EMAIL PROTECTED]> writes: > > The manpage makes me think that when malloc is called with 0 > as argument (and no V-flag had been set) the pointer it returns > can actually be used (as a pointer to the so-called "minimal > allocation"). It seems, that firefox "thinks" the same way

Re: Return value of malloc(0)

2006-06-28 Thread Stefan Farfeleder
On Wed, Jun 28, 2006 at 08:10:45PM +0200, Andre Albsmeier wrote: > There is a nice extension for firefox called prefbar. However, > newer versions of prefbar (>=3.3) make firefox die with SIGSEGV, > see http://bugzilla.mozdev.org/show_bug.cgi?id=13809 for details. > The crash happens in libgklayout

Re: Return value of malloc(0)

2006-06-28 Thread joerg
On Wed, Jun 28, 2006 at 08:10:45PM +0200, Andre Albsmeier wrote: > (Now malloc returns NULL and firefox doesn't interpret the > result as a pointer to some allocated memory and therefore > doesn't use it). Return NULL for malloc(0) is one of two possible implementations. The other behaviour is to

sysctl network stats

2006-06-28 Thread ros
Hi, I'm doing a piece of software in perl to collect system stats. Now I'm working on network i/o stats, and I want to collect the per interface informations. I just looking for some informations about datas I can collect thought the sysctl call. regards - ros _

Re: Return value of malloc(0)

2006-06-28 Thread Randall Hyde
Hi All, I'm trying to port my compiler from Linux to freeBSD. It looked like a simple job up to the point I ran my flex code through FLEX on freeBSD. When GCC processes lex.yy.c I get a complaint about an illegal numeric constant in yy_get_next_buffer, which is all FLEX generated (or prewritten) co

Re: Return value of malloc(0)

2006-06-28 Thread Steve Kargl
On Wed, Jun 28, 2006 at 06:41:05PM -0700, Randall Hyde wrote: > Hi All, > I'm trying to port my compiler from Linux to freeBSD. It looked like a > simple job up to the point I ran my flex code through FLEX on freeBSD. When > GCC processes lex.yy.c I get a complaint about an illegal numeric constant

Re: Return value of malloc(0)

2006-06-28 Thread Matt Emmerton
- Original Message - From: "Steve Kargl" <[EMAIL PROTECTED]> To: "Randall Hyde" <[EMAIL PROTECTED]> Cc: Sent: Wednesday, June 28, 2006 10:10 PM Subject: Re: Return value of malloc(0) > On Wed, Jun 28, 2006 at 06:41:05PM -0700, Randall Hyde wrote: > > Hi All, > > I'm trying to port my c

FLEX, was Re: Return value of malloc(0)

2006-06-28 Thread Randall Hyde
> > > > Without seeing the code or the actual error message, I'm > guessing the answer is 42. Perhaps, some detail might > be appropriate. I seriously doubt seeing the code will do much good. Here's the offending line: YY_INPUT( (&yy_current_buffer->yy_ch_buf[number_to_move]), yy_n_chars,

Re: Return value of malloc(0)

2006-06-28 Thread Johannes Weiner
Hi, On Wed, Jun 28, 2006 at 08:10:45PM +0200, Andre Albsmeier wrote: > "If you use malloc(0) and are crazy enough to access the 'allocated' > memory we give you a SIGSEV to show you how dumb you are :-)". They should check the return value of malloc() in any case for successful allocation.. shoul

Re: FLEX, was Re: Return value of malloc(0)

2006-06-28 Thread Steve Kargl
On Wed, Jun 28, 2006 at 10:40:45PM -0700, Randall Hyde wrote: > > > > > > > Without seeing the code or the actual error message, I'm > > guessing the answer is 42. Perhaps, some detail might > > be appropriate. > > I seriously doubt seeing the code will do much good. > Here's the offending line:

Re: FLEX, was Re: Return value of malloc(0)

2006-06-28 Thread Peter Jeremy
On Wed, 2006-Jun-28 22:40:45 -0700, Randall Hyde wrote: >I seriously doubt seeing the code will do much good. >Here's the offending line: > > YY_INPUT( (&yy_current_buffer->yy_ch_buf[number_to_move]), > yy_n_chars, num_to_read ); How about feeding the C source through the preprocessor, strippi