On Wed, Nov 18, 2020 at 09:05:57PM +0100, Pier Carlo Chiodi wrote:
> Hi,
>
> thanks a lot, I've managed to test it and I confirm that works fine.
>
> Can you confirm whether it will be included in 2.0.8?
Yes
--
Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.
Hi,
thanks a lot, I've managed to test it and I confirm that works fine.
Can you confirm whether it will be included in 2.0.8?
Thanks,
Pier Carlo
On Sun, 15 Nov 2020 at 16:07, Ondrej Zajicek wrote:
> On Sun, Nov 01, 2020 at 02:36:40PM +0100, Pier Carlo Chiodi wrote:
> > Hello, was anyone els
On Sun, Nov 01, 2020 at 02:36:40PM +0100, Pier Carlo Chiodi wrote:
> Hello, was anyone else able to reproduce this issue?
> I've been able to reproduce it also using the code from master.
>
> I paste some more info here, I hope they'll be useful to troubleshoot it.
>
> Thanks
Hi
Sorry for late
On Sun, Nov 01, 2020 at 02:36:40PM +0100, Pier Carlo Chiodi wrote:
> Hello, was anyone else able to reproduce this issue?
> I've been able to reproduce it also using the code from master.
Hello
Thanks for the bugreport and backtrace. Now i have an idea what
causes the issue and how to reproduce i
e
Program received signal SIGSEGV, Segmentation fault.
0x55b5c20d8eb1 in net_format (N=0xcdcdcdcdcdcdcde5, buf=0x7ffc6c8d0570
"", buflen=257) at lib/net.c:82
82 switch (n->n.type)
(gdb)
(gdb)
(gdb) bt
#0 0x55b5c20d8eb1 in net_format (N=0xcdcdcdcdcdcdcde5,
buf=0x
Hello,
I'm getting a "Segmentation fault" error on BIRD 2.0.7 when I use 'receive
limit X'. I've got the error when using either 'action block' or 'action
disable'. In the same scenario, if I change the config to use 'import limit
X' eve
On 13.08.2019 17:45, Maria Jan Matejka wrote:
define myvar = false;
function something () {
if myvar then {
return false;
}
return true;
}
protocol device DEVICE {
}
Could this be because of the new filter code or something else?
Hello
Thanks for bugreport. Yes, it
>> define myvar = false;
>>
>> function something () {
>> if myvar then {
>> return false;
>> }
>>
>> return true;
>> }
>>
>> protocol device DEVICE {
>>
>> }
>>
>> Could this be because of the new filter code or something else?
>
> Hello
>
> Thanks for bugreport. Yes, it is t
On Sat, Aug 10, 2019 at 02:22:18PM +0300, Radu Anghel wrote:
> Hello,
>
> I recently upgraded BIRD from 2.0.4 to 2.0.5 and with the same (pretty
> large) .conf I got Segmentation fault.
>
> Until today I didn't have time to debug it, but here it goes:
>
> With this
Hello,
I recently upgraded BIRD from 2.0.4 to 2.0.5 and with the same (pretty
large) .conf I got Segmentation fault.
Until today I didn't have time to debug it, but here it goes:
With this simple .conf I get seg fault on 2.0.5 while 2.0.4 works as
expected. (if I define myvar = true it do
On 7/30/19 3:01 PM, Илья Шипицин wrote:
> are you going to make new release ?
Surely, we're just finalizing the new features and fixing last found bugs. It's
to be released soon.
Maria
smime.p7s
Description: S/MIME Cryptographic Signature
are you going to make new release ?
вт, 30 июл. 2019 г. в 15:23, Maria Jan Matejka :
> On 7/28/19 6:35 PM, Ondrej Zajicek wrote:
> > On Sun, Jul 28, 2019 at 06:58:06PM +0500, Илья Шипицин wrote:
> >> hello,
> >>
> >> I'm running bird git-master
> >>
> >> ...
> >> on SIGHUP sometimes bird crashes
On 7/28/19 6:35 PM, Ondrej Zajicek wrote:
> On Sun, Jul 28, 2019 at 06:58:06PM +0500, Илья Шипицин wrote:
>> hello,
>>
>> I'm running bird git-master
>>
>> ...
>> on SIGHUP sometimes bird crashes
>>
>>
>> (gdb) bt
>> #0 _IO_vfprintf_internal (s=0x0, format=0x4ddaf9 "%s <%s> ",
>> ap=ap@entry=0x7f9
On Sun, Jul 28, 2019 at 06:58:06PM +0500, Илья Шипицин wrote:
> hello,
>
> I'm running bird git-master
>
> ...
> on SIGHUP sometimes bird crashes
>
>
> (gdb) bt
> #0 _IO_vfprintf_internal (s=0x0, format=0x4ddaf9 "%s <%s> ",
> ap=ap@entry=0x7f9954af06d8)
...
> in case someone interested, plea
hello,
I'm running bird git-master
config (OSPF +BFD):
log "/var/log/bird.log" all;
debug protocols all;
router id X.X.X.X;
filter deny_default {
if net = 0.0.0.0/0 then reject;
else accept;
}
filter permit_white {
if net ~ [ X.X.X.X/32
,X.X.X.X/32,X.X.X.X/32
] then
On Thu, Jul 19, 2018 at 10:33:35AM +0200, Julian Schuh wrote:
> Hi everyone,
>
> while poking around with bird I stumbled upon a reproducible segmentation
> fault in the radv protocol (I think).
Hi
Thanks for the bugreport, attached patch should fix it. Simple workaround
is to di
Hi everyone,
while poking around with bird I stumbled upon a reproducible segmentation fault
in the radv protocol (I think).
I’m using bird 2.0.2 with the following config (simplified for debugging
purposes):
log syslog all;
debug protocols all;
protocol device { }
protocol radv
On Tue, 23 Jan 2018 16:14:28 +0200,
Ondrej Zajicek wrote:
> Attached patch should fix it.
>
Hello,
It does. Thank you!
On Fri, Jan 19, 2018 at 04:22:24PM +0200, Petko Bordjukov wrote:
> Hello,
>
> Example config file that causes the SEGFAULT:
>
> router id 192.168.1.1;
>
> protocol kernel {
> merge paths;
> ipv6 {
> export all;
> };
> }
Hello
Attached patch should fix it
On Fri, Jan 19, 2018 at 04:22:24PM +0200, Petko Bordjukov wrote:
> Hello,
>
> Example config file that causes the SEGFAULT:
>
> router id 192.168.1.1;
>
> protocol kernel {
> merge paths;
> ipv6 {
> export all;
> };
> }
>
> I am able to provide core dump
Hello,
Example config file that causes the SEGFAULT:
router id 192.168.1.1;
protocol kernel {
merge paths;
ipv6 {
export all;
};
}
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x56445cef23ea in krt_set_merge_paths (cc=0x0, merge=1
On Wed, Dec 27, 2017 at 06:20:44PM +0100, Clemens Schrimpe wrote:
> The fix came from Ondrej Zajicek, who also -I think- put it back upstream?!
No, that fix is just workaround, i did not make yet a proper fix for
the upstream.
--
Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: sa
], SA_RESTORER, 0x7f08899e9390},
>>> {SIG_DFL, [], SA_RESTORER, 0x7f08899e9390}, 8) = 0
>>> rt_sigaction(SIGTTOU, {0x7f0889e45b60, [], SA_RESTORER, 0x7f08899e9390},
>>> {SIG_DFL, [], SA_RESTORER, 0x7f08899e9390}, 8) = 0
>>> rt_sigaction(SIGTTIN, {0x7f0889e45b60,
igaction(SIGTTIN, {0x7f0889e45b60, [], SA_RESTORER, 0x7f08899e9390},
> {SIG_DFL, [], SA_RESTORER, 0x7f08899e9390}, 8) = 0
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> rt_sigaction(SIGWINCH, {0x7f0889e45110, [], SA_RESTORER|SA_RESTART,
> 0x7f08899e9390}, {SIG_DFL, [], SA_RESTORER, 0x7f08899e9
t_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> rt_sigaction(SIGWINCH, {0x7f0889e45110, [], SA_RESTORER|SA_RESTART,
> 0x7f08899e9390}, {SIG_DFL, [], SA_RESTORER, 0x7f08899e9390}, 8) = 0
> read(0, "A", 1) = 1
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAP
ction(SIGTTIN, {0x7f0889e45b60, [], SA_RESTORER, 0x7f08899e9390},
> {SIG_DFL, [], SA_RESTORER, 0x7f08899e9390}, 8) = 0
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> rt_sigaction(SIGWINCH, {0x7f0889e45110, [], SA_RESTORER|SA_RESTART,
> 0x7f08899e9390}, {SIG_DFL, [], SA_RESTORER, 0x7f08899e9390
_MAPERR, si_addr=0x8} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
2017-12-27 17:20 GMT+01:00 Michael McConnell :
> Try running
>
> strace -f bird -f -u bird -g bird
>
> and providing the last 20 or 30 lines of the output.
>
> --
>
>
> On Dec 27, 2017, at 10:01 AM, Mike Neo wrote:
>
> Hi,
>
> using up arrow in birdc causes segmentation fault:
>
>
>
> syslog:
>
> Dec 27 16:55:56 r1 kernel: [331700.979873] birdc[15259] segfault at 0 ip
> 7fab7221ba0b sp 7ffef0ee16c8 error 4 i
Hi,
using up arrow in birdc causes segmentation fault:
[image: Obraz w treści 1]
*syslog:*
Dec 27 16:55:56 r1 kernel: [331700.979873] birdc[15259] segfault at 0 ip
7fab7221ba0b sp 7ffef0ee16c8 error 4 in
libreadline.so.6.3[7fab721ed000+3d000]
*environment:*
Description
29 matches
Mail list logo
