El día Tuesday, September 16, 2008 a las 11:25:44AM -0400, John Baldwin
escribió:
> Well, fd_ofiles being NULL here is really odd. It's also odd that you have
> no
> current directory. Because fd_nfiles is 20, fd_ofiles should be pointing to
> the static file descriptor array. Off the top o
On Wednesday 10 September 2008 20:09, John Baldwin wrote:
> On Wednesday 10 September 2008 04:19:30 am Marc Lörner wrote:
> > On Tuesday 09 September 2008 21:38, John Baldwin wrote:
> > > On Thursday 04 September 2008 08:00:04 am Marc Lörner wrote:
> > > > Hello,
> > > > I just read through the cod
Hi all.
We have loadable kernel module with
several syscall intercepting functions
(e.g., sysent[SYS___sysctl].sy_call).
Earlier, this module was built and used
on i386 platform, now we have to run it
on amd64. For some reasons we have to
enable COMPAT_IA32 option in kernel.
Our syscall wrapper s
Hi Hackers, im wondering if its posible somehow to auto reconnect after a
connection fails. This is because from time to time my ISP while renews the
ip address the connection just freezes and i have to manually use dhclient
-u {if} to get the new address or even when there is no ip change by my IS
On Tuesday 16 September 2008 04:07:46 pm Navdeep Parhar wrote:
> Hello everyone,
>
> The add-kld command in kgdb does not work as expected on amd64
> (I'm using a recent HEAD, problem may affect others too). It uses
> the same address for all sections:
>
> (kgdb) add-kld if_cxgb.ko
> add symbol
Andrew N. Below wrote:
Hi all.
We have loadable kernel module with
several syscall intercepting functions
(e.g., sysent[SYS___sysctl].sy_call).
Earlier, this module was built and used
on i386 platform, now we have to run it
on amd64. For some reasons we have to
enable COMPAT_IA32 option in kerne
[If this is not an appropriate forum for this query, please suggest
a more appropriate one]
In investigating a Python 2.6rc1 regression test failure on FreeBSD
7.0/amd64, as far as I can tell, malloc() does not return NULL when
available memory (including swap) is exhausted - the process just get
> Andrew N. Below wrote:
> > Hi all.
> >
> > We have loadable kernel module with
> > several syscall intercepting functions
> > (e.g., sysent[SYS___sysctl].sy_call).
> > Earlier, this module was built and used
> > on i386 platform, now we have to run it
> > on amd64. For some reasons we have to
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Andrew MacIntyre wrote:
[snip]
| In investigating a Python 2.6rc1 regression test failure on FreeBSD
| 7.0/amd64, as far as I can tell, malloc() does not return NULL when
| available memory (including swap) is exhausted - the process just gets
| KIL
> x86 binaries use a separate syscall table, so you need to patch
> both tables.
Ooops, sorry, I found it.
Thanks!
--
Andrew
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any
Andrew MacIntyre wrote:
In investigating a Python 2.6rc1 regression test failure on FreeBSD
7.0/amd64, as far as I can tell, malloc() does not return NULL when
available memory (including swap) is exhausted - the process just gets
KILLed.
Using ulimit -v to set a virtual memory use limit below t
On Wednesday 17 September 2008 09:51:22 am Andrew N. Below wrote:
> Hi all.
>
> We have loadable kernel module with
> several syscall intercepting functions
> (e.g., sysent[SYS___sysctl].sy_call).
> Earlier, this module was built and used
> on i386 platform, now we have to run it
> on amd64. For s
On 9/17/08, Eygene Ryabinkin <[EMAIL PROTECTED]> wrote:
> Maxim, good day.
>
> Cc'ing this discuission to hackers@ -- I was just going to write
> the separate letter on this topic to the list.
>
> Wed, Sep 17, 2008 at 09:56:14AM -0700, Maksim Yevmenkin wrote:
> > have you tried to simply set KB
Andrew N. Below wrote:
Andrew N. Below wrote:
Hi all.
We have loadable kernel module with
several syscall intercepting functions
(e.g., sysent[SYS___sysctl].sy_call).
Earlier, this module was built and used
on i386 platform, now we have to run it
on amd64. For some reasons we have to
enable COM
Hello John,
The patch did NOT fix the problem. Read on for more
On Wed, Sep 17, 2008 at 8:31 AM, John Baldwin <[EMAIL PROTECTED]> wrote:
> On Tuesday 16 September 2008 04:07:46 pm Navdeep Parhar wrote:
>> Hello everyone,
>>
>> The add-kld command in kgdb does not work as expected on amd64
>>
Maxim, good day.
Cc'ing this discuission to hackers@ -- I was just going to write
the separate letter on this topic to the list.
Wed, Sep 17, 2008 at 09:56:14AM -0700, Maksim Yevmenkin wrote:
> have you tried to simply set KBDMUX_LOCK/UNLOCK() to
> mtx_lock/unlock(&Giant) ?
Since kbdmux callout
On Wed, 17 Sep 2008, Julian Elischer wrote:
Seems like these calls are made bypassing
our kernel module.
x86 binaries use a separate syscall table, so you need to patch
both tables.
Where can I find something about that table?
the compat stuff is in /sys/compat/ia32/
So I would start there an
On Wednesday 17 September 2008 03:51:02 pm Navdeep Parhar wrote:
> Hello John,
>
> The patch did NOT fix the problem. Read on for more
>
> On Wed, Sep 17, 2008 at 8:31 AM, John Baldwin <[EMAIL PROTECTED]> wrote:
> > On Tuesday 16 September 2008 04:07:46 pm Navdeep Parhar wrote:
> >> Hello ev
may you could use ifstated, it is a FSM (finit state machine) may could help
http://www.openbsd.org/cgi-bin/man.cgi?query=ifstated&sektion=8
cheers
2008/9/17, Andres Chavez <[EMAIL PROTECTED]>:
> Hi Hackers, im wondering if its posible somehow to auto reconnect after a
> connection fails. This i
Jason Evans wrote:
Andrew MacIntyre wrote:
In investigating a Python 2.6rc1 regression test failure on FreeBSD
7.0/amd64, as far as I can tell, malloc() does not return NULL when
available memory (including swap) is exhausted - the process just gets
KILLed.
Using ulimit -v to set a virtual memo
Andrew MacIntyre wrote:
However my reading of the updated man page suggests that the malloc
options string should be "Dm" or "m" to turn off mmap() and only use
sbrk() - could you clarify why "d"?
Whoops, I meant "m", not "d".
Jason
___
freebsd-hacke
21 matches
Mail list logo