Re: ud segfault (was: When will the amd64 port be stable?)

2004-12-12 Thread Ron Johnson
On Sun, 2004-12-12 at 05:18 +, Steve McIntyre wrote: David Liontooth [EMAIL PROTECTED] wrote: Goswin von Brederlow wrote: [snip] The reason for this becomes clear once you turn on warnings in the compilation: gcc -DPACKAGE=\ud\ -DVERSION=\0.7.1\ -DSTDC_HEADERS=1 -DHAVE_UNISTD_H=1

Re: ud segfault (was: When will the amd64 port be stable?)

2004-12-12 Thread Steve McIntyre
[EMAIL PROTECTED] wrote: On Sun, 2004-12-12 at 05:18 +, Steve McIntyre wrote: The reason for this becomes clear once you turn on warnings in the compilation: gcc -DPACKAGE=\ud\ -DVERSION=\0.7.1\ -DSTDC_HEADERS=1 -DHAVE_UNISTD_H=1 -DRETSIGTYPE=void -DHAVE_GETHOSTNAME=1 -I. -I. -g

Re: ud segfault (was: When will the amd64 port be stable?)

2004-12-12 Thread Ron Johnson
On Sun, 2004-12-12 at 12:39 +, Steve McIntyre wrote: [EMAIL PROTECTED] wrote: On Sun, 2004-12-12 at 05:18 +, Steve McIntyre wrote: [snip] Turning on warnings also highlights other silly coding bugs, but I'll leave those for other people. Hey, let's start a flame war about the

Re: Bug#271758: ud segfault (was: When will the amd64 port be stable?)

2004-12-12 Thread Steve Kemp
On Sun, Dec 12, 2004 at 05:18:37AM +, Steve McIntyre wrote: David Liontooth [EMAIL PROTECTED] wrote: Goswin von Brederlow wrote: And now the same with -f please. I didn't see a segfault in the starce and it is probably its child that dies. You can also compile the ud with debug infos

Re: ud segfault

2004-12-12 Thread David Liontooth
Steve McIntyre wrote: OK, so I'm bored. I've just looked at the bug and found the problem. ud's source is quite ugly, suggesting a novice author. I can recreate the bug quite readily here, and it's crashing down below a sprintf() call: (gdb) bt #0 0x002a956e9980 in strlen () from

ud segfault (was: When will the amd64 port be stable?)

2004-12-11 Thread David Liontooth
Goswin von Brederlow wrote: David Liontooth [EMAIL PROTECTED] writes: Dec 11 12:59:13 clitunno ud[6280]: Uptime daemon starting... Dec 11 12:59:13 clitunno kernel: ud[6280]: segfault at 958a7d00 rip 002a956e9980 rsp 007fbfffecb8 error 4 The daemon really does stop running, every

Re: ud segfault

2004-12-11 Thread Goswin von Brederlow
David Liontooth [EMAIL PROTECTED] writes: Hi Goswin, So this is not behavior others are seeing? I have the pleasure of sending you a thousand EBADF reports below -- I have no clue. I don't have ud installed and know of noone having it running. I'm just trying to guide you to finding the

Re: ud segfault (was: When will the amd64 port be stable?)

2004-12-11 Thread Steve McIntyre
David Liontooth [EMAIL PROTECTED] wrote: Goswin von Brederlow wrote: And now the same with -f please. I didn't see a segfault in the starce and it is probably its child that dies. You can also compile the ud with debug infos and run it in gdb. MfG Goswin Hi Goswin, So this is not