Conversation
jarkko

Jarkko Sakkinen

#mbsync always crashes here in #Fedora (even when compiled from upstream):

Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000055d33068a967 in sync_chans (mvars=0x7ffef80ee330, ent=<optimized out>) at /usr/src/debug/isync-1.4.4-8.fc40.x86_64/src/main.c:906
906 char *sname = boxes[N] ? boxes[N][sb] : NULL;

Any ideas? I used coredumpctl to discover this location but for comparative testing I also compiled the latest upstream of mbsync, and it crashes in the exact same location.

#isync
1
0
0
adamw@fosstodon.org

Adam Williamson fedora

Reply to @jarkko

@jarkko you should be able to use `coredumpctl gdb` to get a full backtrace of the crash, which you can attach to a bug report - https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&format=

1
0
0
jarkko

Jarkko Sakkinen

Reply to @adamw@fosstodon.org
@adamw Yeah, that is what I used for the transcript. Thanks, I'll put out a bug report!
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
@adamw I reported it https://bugzilla.redhat.com/show_bug.cgi?id=2302132. I can review kernel patches with my Mac mini up until this is fixed ;-) Still a bit inconvenient workflow I think as I need to do all testing in my Fedora box.
1
0
0
gromit@chaos.social

Christian Heusel

Reply to @jarkko
Edited 3 months ago

@jarkko @adamw could you also attach the output of the gdb backtrace to the bugreport?

1
0
0
jarkko

Jarkko Sakkinen

Reply to @gromit@chaos.social
@gromit @adamw It is inline there but yeah sure I can also attach it.
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko

@gromit @adamw I added couple:

  1. e70c300f7446 (“permit leading whitespace in INTERNALDATE strings”)
  2. isync-1.4.4-8.fc40.x86_64

Upstream was compiled with the usual autogen.sh && ./configure && make flow.

0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: