On Jun 22, 2017, at 6:23 AM, Warren Young <[email protected]> wrote:
>
>> Can you provide a test case?
>
> I can’t share the repo, but I’ve dropped an abort() in front of the line I
> referenced in the prior email, so sometime today I should have a backtrace
> for you.
Well, here it is, but it just looks like a more elaborate version of what I
wrote in the bug report:
#0 0x00007f9ff43051d7 in raise () from /lib64/libc.so.6
#1 0x00007f9ff43068c8 in abort () from /lib64/libc.so.6
#2 0x000000000041cd27 in prompt_for_user_comment
(pComment=pComment@entry=0x7ffc3bb9b0c0, pPrompt=pPrompt@entry=0x7ffc3bb9b1a0)
at ./src/checkin.c:1225
#3 0x000000000041f103 in prepare_commit_comment (parent_rid=111752,
p=0x7ffc3bb9b200, zInit=0x0, pComment=0x7ffc3bb9b0c0) at ./src/checkin.c:1339
#4 commit_cmd () at ./src/checkin.c:2317
#5 0x0000000000409324 in main (argc=<optimized out>, argv=<optimized out>) at
./src/main.c:770
Thinking that maybe Vim on this system is just too piggy (EDITOR=vim) I tried
setting EDITOR to nano and to Heirloom Vi, both of which do the same thing.
Telling gdb to trace into the child process doesn’t give anything useful.
I even wrote this shell script and set it as EDITOR, and got a core dump before
the strace command even gets started:
#!/bin/sh
strace vim "$@“
I’m out of ideas.
_______________________________________________
fossil-dev mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
