|
|
Up |
|
|
  |
Author: DasnDasn
Date: Apr 4, 2008 15:21
I think the shmget(2) can produce EINVAL, which is not mentioned in
its manual page.
$ cat test.c
#include
#include
#include
#include
#define SHMKEY 75
#define K 1024
int
main(void)
{
int shmid;
if ((shmid = shmget(SHMKEY, 64 * K, IPC_CREAT)) == -1)
perror("shmget first");
if ((shmid = shmget(SHMKEY, (64+1) * K, IPC_CREAT)) == -1)
perror("shmget second");
exit(0);
}
|
| Show full article (1.01Kb) |
|
| |
no comments
|
|
  |
Author: RD ThrushRD Thrush
Date: Apr 4, 2008 13:01
For almost 2 weeks I have had both amd64 and i386 kernels hang. The
problem first occurred while updating -current ports since the libc
bump. I've found the hang is triggered more quickly by building the
eclipse-sdk port. The hang has occurred on 3 different machines.
Entering ddb always show one process WAITing on "no_fltram5"
(usually javadoc). The hung machines are usually pingable, KB leds
always work and ddb can be entered from the keyboard. A full
problem report, kernel/5777 [1], including dmesgs and ddb report was
filed on 3/23/2008. I have since updated that report with details
about the subsequent hangs found on a Sempron and amd64 laptop.
Sorry to trouble tech@ but no response to the bug report or the 3/27
report on misc@ prompted me to make sure the report hasn't fallen
through the cracks. I suspect getting 4.3 out the door is occupying
serious developer time so no panic.
Let me know if there is further information that would be helpful to
analyze / solve this problem.
[1] < http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&textonly=yes&numbers=57...>
|
| |
|
| |
no comments
|
|
  |
|
|
  |
Author: gleydson soaresgleydson soares
Date: Apr 4, 2008 10:10
Index: pfctl.c
===================================================================
RCS file: /cvs/src/sbin/pfctl/pfctl.c,v
retrieving revision 1.273
diff -u -r1.273 pfctl.c
--- pfctl.c 13 Feb 2008 19:55:12 -0000 1.273
+++ pfctl.c 3 Apr 2008 21:01:13 -0000
@@ -56,7 +56,7 @@
#include "pfctl_parser.h"
#include "pfctl.h"
-void usage(void);
+__dead void usage(void);
int pfctl_enable(int, int);
int pfctl_disable(int, int);
int pfctl_clear_stats(int, int);
@@ -221,7 +221,7 @@
"none", "basic", "profile", NULL
};
|
| Show full article (0.60Kb) |
|
no comments
|
|
  |
Author: Pierre RiteauPierre Riteau
Date: Apr 4, 2008 10:10
Hi.
There's code in aucat.c which tries to reopen the audio device every
time we play a file if it wasn't open, but if we can't open the device
at the very beginning we err(), so this code is useless.
While here, switch usage to __dead.
Pierre Riteau
Index: aucat.c
===================================================================
RCS file: /home/priteau/cvs/src/usr.bin/aucat/aucat.c,v
retrieving revision 1.13
diff -p -u -r1.13 aucat.c
--- aucat.c 20 Mar 2007 23:35:15 -0000 1.13
+++ aucat.c 3 Apr 2008 20:23:48 -0000
@@ -46,11 +46,11 @@
* uncompressed WAVE RIFF files
*/
|
| Show full article (2.11Kb) |
|
no comments
|
|
  |
Author: Amarendra GodboleAmarendra Godbole
Date: Apr 4, 2008 10:09
On Fri, Mar 28, 2008 at 3:20 PM, Amarendra Godbole
gmail.com> wrote:
> On Fri, Mar 28, 2008 at 2:40 PM, Matthieu Herrb wrote:
>>
>> You need 3 things after the recent changes in the xenocara build system:
>>
>> - make sure your base system is current first (at least /usr/share/mk
>> should contain the new bsd.xconf.mk file)
>
> It is.
> # $OpenBSD: bsd.xconf.mk,v 1.1 2008/03/25 23:35:56 matthieu Exp $
>
>
>> - wipe you ${XOBJDIR} before starting the xenocara build
>> - run 'make bootstrap', then 'make obj', then 'make build'.
>
> No luck. Same issues as earlier. Now that it works for you, most
> likely then it is a local problem for me. Let me see what can I find
> out, and I shall post my findings. Thanks.
[...] ...
|
| Show full article (1.92Kb) |
|
no comments
|
|
  |
|
|
  |
Author: Devin SmithDevin Smith
Date: Apr 4, 2008 10:02
Hi,
I can not seem to figure out why I can't debug some programs on
OpenBSD/macppc. It seems to me that the -ggdb3 switch given to gcc is
broken on macppc. I've created a sample program that should show the
problem. Please compile it with the -ggdb3 flag and then you can see
the problem if you put a breakpoint in read_struct with gdb. What
happens is that the variables in the argument list are incorrect.
Also, if you take away the extra buf[512] the problem goes away. In my
opinion the stack is messed up. The unused variable buf is not
required for this program but it's there to illustrate the problem
since it is required for some larger more complicated programs.
I can get around the problem if I use the -g switch instead of -ggdb3.
The -ggdb3 flag works fine on i386 (the only other machine I have to
test on). I would be curious to see if this switch also works on
other architectures.
Is this a known problem?
#include
#include
|
| Show full article (2.28Kb) |
|
no comments
|
|
  |
|
|
  |
|
|
  |
Author: Tim van der MolenTim van der Molen
Date: Apr 4, 2008 09:51
On Wed, 19 Mar 2008 00:56:13 +0100, Tim van der Molen wrote:
> This diff makes cwm's `exec' dialogues search for executables in $PATH
> first before falling back on the default path. This also matches the
> behaviour of execvp(3) (which is used to execute the selected
> executable).
>
> I removed the comment because I think that with this change, no further
> configuration would be required here.
Assuming there are no objections, could someone please commit this?
Thanks.
Regards,
Tim
|
| Show full article (1.21Kb) |
|
no comments
|
|
|
|
|
|
|