On Wed, Dec 18, 2024 at 12:26:37AM +0100, nick wrote:
> Hey,
>
> I did a PR for the routing feed containing your latest patch [0]. I hope
> everything is alright. I'm looking forward to the BIRD 3 release. If I need
> to test something, I'm happy to help. I can also give you SSH access via
> IPv6
Hey,
I did a PR for the routing feed containing your latest patch [0]. I hope
everything is alright. I'm looking forward to the BIRD 3 release. If I
need to test something, I'm happy to help. I can also give you SSH
access via IPv6 to an OpenWrt device for testing, if you'd like.
[0] - https
On Mon, Dec 16, 2024 at 05:43:16PM +0100, nick wrote:
> Dear all,
>
> Apologies for the earlier confusion—my toolchain was misconfigured, and I
> mistakenly compiled the unpatched BIRD sources. Upon correcting this, I
> believe the first patch already addresses the issue. However, I noticed that
>
Dear all,
Apologies for the earlier confusion—my toolchain was misconfigured, and
I mistakenly compiled the unpatched BIRD sources. Upon correcting this,
I believe the first patch already addresses the issue. However, I
noticed that the two patches result in different alignments. Below is a
s
On Thu, Dec 12, 2024 at 12:50:31AM +0100, nick wrote:
> Can you give me a quick guide on how to enable the debug output?
> I tried for example setting in the config file:
>
> > log "/tmp/birddebug.log" all;
> > debug protocols all;
>
> I am not able to see any output from ALIGN.
As the log messa
Can you give me a quick guide on how to enable the debug output?
I tried for example setting in the config file:
log "/tmp/birddebug.log" all;
debug protocols all;
I am not able to see any output from ALIGN.
On 12/11/24 4:40 AM, Ondrej Zajicek wrote:
On Wed, Dec 11, 2024 at 02:14:39AM +0100,
On Wed, Dec 11, 2024 at 02:14:39AM +0100, nick wrote:
> Thank you! I just ran a quick test and encountered the same crash at the
> same line. I’ll have more time to investigate tomorrow and can provide
> additional details then. Do you have any other ideas I could try in the
> meantime?
A part of
On Tue, Dec 10, 2024 at 09:15:46PM +0100, nick via Bird-users wrote:
> I also uploaded the coredumpfile:
> https://github.com/PolynomialDivision/coredumpupload/blob/main/bird_coredump
Thanks. This seems like an interesting issue. In BIRD, generic net_addr
structure is explicitly u64-aligned (to ac
Thank you! I just ran a quick test and encountered the same crash at the
same line. I’ll have more time to investigate tomorrow and can provide
additional details then. Do you have any other ideas I could try in the
meantime?
Core dump:
https://github.com/PolynomialDivision/coredumpupload/tree
I also uploaded the coredumpfile:
https://github.com/PolynomialDivision/coredumpupload/blob/main/bird_coredump
On 12/10/24 8:56 PM, nick via Bird-users wrote:
Sorry for the long response time.
Here is the requested output:
Program received signal SIGBUS, Bus error.
0x00056fc0 in bgp_get_prefi
Sorry for the long response time.
Here is the requested output:
Program received signal SIGBUS, Bus error.
0x00056fc0 in bgp_get_prefix (path_id=0, net=0xb6f0709c, c=0xb6ee9bc0)
at proto/bgp/attrs.c:1710
1710 proto/bgp/attrs.c: No such file or directory.
(gdb) p sizeof(struct mblock)
$1 =
On Thu, Dec 05, 2024 at 11:35:13PM +0100, nick via Bird-users wrote:
> Dear BIRD Community,
>
> I am writing to report a bug observed in the BGP implementation on ARMv7
> platforms, which results in a SIGBUS error due to unaligned memory access in
> the NEON assembler code. I debugged this issue o
Dear BIRD Community,
I am writing to report a bug observed in the BGP implementation on ARMv7
platforms, which results in a SIGBUS error due to unaligned memory
access in the NEON assembler code. I debugged this issue on version
2.15.1 of BIRD.
### Problem Description
When running BIRD on A
13 matches
Mail list logo
