On Thu, Mar 14, 2013 at 6:48 PM, Ted Unangst wrote:
> On Thu, Mar 14, 2013 at 17:24, Antoine Jacoutot wrote:
>> On Thu, Mar 14, 2013 at 11:41:52AM -0400, Ted Unangst wrote:
>>> On Thu, Mar 14, 2013 at 14:30, Antoine Jacoutot wrote:
>>>
>>> > FYI I am seeing a somehow similar crash when using sysut
On Thu, Mar 14, 2013 at 12:48:52PM -0400, Ted Unangst wrote:
> On Thu, Mar 14, 2013 at 17:24, Antoine Jacoutot wrote:
> > On Thu, Mar 14, 2013 at 11:41:52AM -0400, Ted Unangst wrote:
> >> On Thu, Mar 14, 2013 at 14:30, Antoine Jacoutot wrote:
> >>
> >> > FYI I am seeing a somehow similar crash when
On Thu, Mar 14, 2013 at 17:24, Antoine Jacoutot wrote:
> On Thu, Mar 14, 2013 at 11:41:52AM -0400, Ted Unangst wrote:
>> On Thu, Mar 14, 2013 at 14:30, Antoine Jacoutot wrote:
>>
>> > FYI I am seeing a somehow similar crash when using sysutils/bacula (both
>> > 5.2 and 5.3).
>> > It is 100% reprodu
On Thu, Mar 14, 2013 at 11:41:52AM -0400, Ted Unangst wrote:
> On Thu, Mar 14, 2013 at 14:30, Antoine Jacoutot wrote:
>
> > FYI I am seeing a somehow similar crash when using sysutils/bacula (both
> > 5.2 and 5.3).
> > It is 100% reproducible on my setup. Obviously painful since it means I
> > can
On Thu, Mar 14, 2013 at 14:30, Antoine Jacoutot wrote:
> FYI I am seeing a somehow similar crash when using sysutils/bacula (both
> 5.2 and 5.3).
> It is 100% reproducible on my setup. Obviously painful since it means I
> cannot run backups anymore...
The following is brought to you without testi
On Thu, Sep 27, 2012 at 12:43:24PM +0300, Alexey Suslikov wrote:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to thread 1006387]
> 0x0cb33345cf6e in random () at /usr/src/lib/libc/stdlib/random.c:387
> 387 *fptr += *rptr;
>
> Back trace:
>
> Thread 1
On Thu, 27 Sep 2012, Alexey Suslikov wrote:
> On Thursday, September 27, 2012, Alexey Suslikov wrote:
> > On Thursday, September 27, 2012, Philip Guenther wrote:
> >> On Thu, 27 Sep 2012, Alexey Suslikov wrote:
> >> > Removing only local variables part reverts us to previous behavior
> >> > (i.e.
On Thursday, September 27, 2012, Alexey Suslikov wrote:
> On Thursday, September 27, 2012, Philip Guenther wrote:
>
>> On Thu, 27 Sep 2012, Alexey Suslikov wrote:
>> > Removing only local variables part reverts us to previous behavior (i.e.
>> > crashes).
>>
>> My guess is your program is calling
On Thursday, September 27, 2012, Philip Guenther wrote:
> On Thu, 27 Sep 2012, Alexey Suslikov wrote:
> > Removing only local variables part reverts us to previous behavior (i.e.
> > crashes).
>
> My guess is your program is calling srandom(), srandomdev(), initstate()
> or setstate() as well. Yo
On Thu, 27 Sep 2012, Alexey Suslikov wrote:
> Removing only local variables part reverts us to previous behavior (i.e.
> crashes).
My guess is your program is calling srandom(), srandomdev(), initstate()
or setstate() as well. Your diff doesn't protect the alteration of state,
end_ptr, fptr, a
On Thu, Sep 27, 2012 at 00:18, Alexey Suslikov wrote:
> On Wed, Sep 26, 2012 at 9:51 PM, Ted Unangst wrote:
>> On Wed, Sep 26, 2012 at 11:18, Alexey Suslikov wrote:
>>> Hi.
>>>
>>> Any news on that?
>>
>> Can we do it without the local variables for speed part? I am not
>> interested in making th
On Wed, Sep 26, 2012 at 9:51 PM, Ted Unangst wrote:
> On Wed, Sep 26, 2012 at 11:18, Alexey Suslikov wrote:
>> Hi.
>>
>> Any news on that?
>
> Can we do it without the local variables for speed part? I am not
> interested in making this function faster.
>
Removing only local variables part rever
On Wed, Sep 26, 2012 at 11:18, Alexey Suslikov wrote:
> Hi.
>
> Any news on that?
Can we do it without the local variables for speed part? I am not
interested in making this function faster.
Hi.
Any news on that?
On Friday, September 21, 2012, Alexey Suslikov wrote:
> On Fri, Sep 21, 2012 at 10:36 AM, Alexey Suslikov
> > wrote:
> > On Wed, Sep 19, 2012 at 10:24 PM, Ted Unangst
> > >
> wrote:
> >> On Wed, Sep 19, 2012 at 18:50, Alexey Suslikov wrote:
> >>> On Wednesday, September 19
On Fri, Sep 21, 2012 at 10:36 AM, Alexey Suslikov
wrote:
> On Wed, Sep 19, 2012 at 10:24 PM, Ted Unangst wrote:
>> On Wed, Sep 19, 2012 at 18:50, Alexey Suslikov wrote:
>>> On Wednesday, September 19, 2012, Theo de Raadt wrote:
>>>
> arc4random() is also thread-safe (it has interal locking)
On Wed, Sep 19, 2012 at 10:24 PM, Ted Unangst wrote:
> On Wed, Sep 19, 2012 at 18:50, Alexey Suslikov wrote:
>> On Wednesday, September 19, 2012, Theo de Raadt wrote:
>>
>>> > arc4random() is also thread-safe (it has interal locking) and very
>>> > desirable for other reasons. But no way to save s
On 2012/09/20 12:04, Paul Irofti wrote:
> On Thu, Sep 20, 2012 at 09:42:16AM +0100, Stuart Henderson wrote:
> > On 2012/09/19 22:06, Stefan Sperling wrote:
> > > On Wed, Sep 19, 2012 at 10:37:09PM +0300, Alexey Suslikov wrote:
> > > > Could you guide me how to rebuild/reinstall libc in a proper way
On Thu, Sep 20, 2012 at 09:42:16AM +0100, Stuart Henderson wrote:
> On 2012/09/19 22:06, Stefan Sperling wrote:
> > On Wed, Sep 19, 2012 at 10:37:09PM +0300, Alexey Suslikov wrote:
> > > Could you guide me how to rebuild/reinstall libc in a proper way?
> >
> > It's easy, just needs 11 steps. This
On Thu, Sep 20, 2012 at 09:42:16AM +0100, Stuart Henderson wrote:
> On 2012/09/19 22:06, Stefan Sperling wrote:
> > On Wed, Sep 19, 2012 at 10:37:09PM +0300, Alexey Suslikov wrote:
> > > Could you guide me how to rebuild/reinstall libc in a proper way?
> >
> > It's easy, just needs 11 steps. This
On Thu, Sep 20, 2012 at 09:15:42AM +0200, Remco wrote:
> AFAICT at least the tools in /bin and /sbin are statically linked and would
> need to be rebuilt to include any changes in libc.
That's correct, and it's actually very convenient.
If you make some mistake dynamic binaries might no longer be
On 2012/09/19 22:06, Stefan Sperling wrote:
> On Wed, Sep 19, 2012 at 10:37:09PM +0300, Alexey Suslikov wrote:
> > Could you guide me how to rebuild/reinstall libc in a proper way?
>
> It's easy, just needs 11 steps. This is how I did it:
>
> 1) $ cd /usr/src/lib/libc
> 2) edit files
> 3) $ make
Stefan Sperling wrote:
> On Wed, Sep 19, 2012 at 10:37:09PM +0300, Alexey Suslikov wrote:
>> Could you guide me how to rebuild/reinstall libc in a proper way?
>
> It's easy, just needs 11 steps. This is how I did it:
>
> 1) $ cd /usr/src/lib/libc
> 2) edit files
> 3) $ make obj
> 4) $ make clean
On Wed, Sep 19, 2012 at 10:37:09PM +0300, Alexey Suslikov wrote:
> Could you guide me how to rebuild/reinstall libc in a proper way?
It's easy, just needs 11 steps. This is how I did it:
1) $ cd /usr/src/lib/libc
2) edit files
3) $ make obj
4) $ make clean
5) $ make
6) pray !!!
7) $ sudo make ins
On Wed, Sep 19, 2012 at 10:24 PM, Ted Unangst wrote:
> On Wed, Sep 19, 2012 at 18:50, Alexey Suslikov wrote:
>> On Wednesday, September 19, 2012, Theo de Raadt wrote:
>>
>>> > arc4random() is also thread-safe (it has interal locking) and very
>>> > desirable for other reasons. But no way to save s
On Wed, Sep 19, 2012 at 18:50, Alexey Suslikov wrote:
> On Wednesday, September 19, 2012, Theo de Raadt wrote:
>
>> > arc4random() is also thread-safe (it has interal locking) and very
>> > desirable for other reasons. But no way to save state.
>>
>> The last part of this is intentional. Saving t
On 09/19/12 10:16, Paul Irofti wrote:
On Tue, Sep 18, 2012 at 05:46:55PM -0700, Marco S Hyman wrote:
On Sep 18, 2012, at 3:27 PM, Paul Irofti wrote:
Because most of the guys in the hackingroom didn't get this, the
reference is to a book named 'American Gods' by Neil Gaimen. Wednesday
is Odin
Op 19 sep. 2012 om 17:28 heeft Theo de Raadt het
volgende geschreven:
>> arc4random() is also thread-safe (it has interal locking) and very
>> desirable for other reasons. But no way to save state.
>
> The last part of this is intentional. Saving the state of pseudo
> random number generators is
On Wednesday, September 19, 2012, Theo de Raadt wrote:
> > arc4random() is also thread-safe (it has interal locking) and very
> > desirable for other reasons. But no way to save state.
>
> The last part of this is intentional. Saving the state of pseudo
> random number generators is a stupid conc
> arc4random() is also thread-safe (it has interal locking) and very
> desirable for other reasons. But no way to save state.
The last part of this is intentional. Saving the state of pseudo
random number generators is a stupid concept from the 80's.
On Tue, Sep 18, 2012 at 05:46:55PM -0700, Marco S Hyman wrote:
> On Sep 18, 2012, at 3:27 PM, Paul Irofti wrote:
>
> > Because most of the guys in the hackingroom didn't get this, the
> > reference is to a book named 'American Gods' by Neil Gaimen. Wednesday
> > is Odin from the Norse Sagas in th
On Tue, Sep 18, 2012 at 09:45:59PM -0400, Ted Unangst wrote:
> On Wed, Sep 19, 2012 at 00:48, Alexey Suslikov wrote:
>
> >> > No, according to posix it should be thread safe. I don't know why,
> >> > since rand() is one of the exempted functions, but random() is not.
> >> > Standards gods are ca
On Wed, Sep 19, 2012 at 00:48, Alexey Suslikov wrote:
>> > No, according to posix it should be thread safe. I don't know why,
>> > since rand() is one of the exempted functions, but random() is not.
>> > Standards gods are capricious gods.
>>
>> I think you should stress *should* here. Looking at
On Sep 18, 2012, at 3:27 PM, Paul Irofti wrote:
> Because most of the guys in the hackingroom didn't get this, the
> reference is to a book named 'American Gods' by Neil Gaimen. Wednesday
> is Odin from the Norse Sagas in that book.
Gaiman, not Gaimen. http://www.neilgaiman.com/
> Pretty awesom
On 2012/09/19 01:27, Paul Irofti wrote:
> Because most of the guys in the hackingroom didn't get this
inconceivable!
On Tue, Sep 18, 2012 at 12:55:40PM -0700, Philip Guenther wrote:
> On Tue, 18 Sep 2012, Marc Espie wrote:
> > On Tue, Sep 18, 2012 at 01:39:14PM -0600, Theo de Raadt wrote:
> > > > Standards gods are capricious gods.
> > >
> > > They are false gods.
> >
> > Sounds like American gods :)
>
> Maybe
On Tuesday, September 18, 2012, Otto Moerbeek wrote:
> On Tue, Sep 18, 2012 at 03:32:04PM -0400, Ted Unangst wrote:
>
> > On Tue, Sep 18, 2012 at 19:40, Alexey Suslikov wrote:
> >
> > > This one being discovered by Roman Kravchuk using Kannel port (see
> > > https://github.com/jasperla/openbsd-wip
On Tue, Sep 18, 2012 at 03:32:04PM -0400, Ted Unangst wrote:
> On Tue, Sep 18, 2012 at 19:40, Alexey Suslikov wrote:
>
> > This one being discovered by Roman Kravchuk using Kannel port (see
> > https://github.com/jasperla/openbsd-wip/tree/master/net/kannel).
> >
> > While stress testing, Kannel
On Tue, Sep 18, 2012 at 01:39:14PM -0600, Theo de Raadt wrote:
> > Standards gods are capricious gods.
>
> They are false gods.
Sounds like American gods :)
On Tue, 18 Sep 2012, Marc Espie wrote:
> On Tue, Sep 18, 2012 at 01:39:14PM -0600, Theo de Raadt wrote:
> > > Standards gods are capricious gods.
> >
> > They are false gods.
>
> Sounds like American gods :)
Maybe "Standards" is the god that no one can remember that Wednesday meets
in Las Vegas
> Standards gods are capricious gods.
They are false gods.
On Tue, Sep 18, 2012 at 19:40, Alexey Suslikov wrote:
> This one being discovered by Roman Kravchuk using Kannel port (see
> https://github.com/jasperla/openbsd-wip/tree/master/net/kannel).
>
> While stress testing, Kannel components die with
>
> Program received signal SIGSEGV, Segmentation fau
Hello tech@.
This one being discovered by Roman Kravchuk using Kannel port (see
https://github.com/jasperla/openbsd-wip/tree/master/net/kannel).
While stress testing, Kannel components die with
Program received signal SIGSEGV, Segmentation fault.
[Switching to thread 1006387]
0x0cb33345cf6e
42 matches
Mail list logo
