Segfault on command line generation

Umair Khan ukhan at pdx.edu
Fri Jul 3 21:36:45 BST 2020


Hello, thanks for the response. The command I am using is: kstars --dump --filename kstars.png --height 640 --width 480. I got the command from this page in the handbook: https://docs.kde.org/trunk5/en/extragear-edu/kstars/dumpmode.html
I also just ran it with gdb. Below is the backtrace.
...
Loading satellites
[New Thread 0x7fffb7659700 (LWP 16238)]
QPaintDevice: Cannot destroy paint device that is being painted
Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0x00007ffff30da7a6 in QPainter::end() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
(gdb) bt
#0 0x00007ffff30da7a6 in QPainter::end() () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#1 0x00007ffff30db3f8 in QPainter::~QPainter() () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#2 0x0000555555b2ad28 in SkyLabeler::~SkyLabeler() (this=0x555556a94000, __in_chrg=<optimized out>) at ./kstars/skycomponents/skylabeler.cpp:111
#3 0x0000555555679f01 in std::default_delete<SkyLabeler>::operator()(SkyLabeler*) const (this=<optimized out>, __ptr=0x555556a94000) at /usr/include/c++/7/bits/unique_ptr.h:78
#4 0x0000555555679f01 in std::unique_ptr<SkyLabeler, std::default_delete<SkyLabeler> >::~unique_ptr() (this=0x5555569549b8, __in_chrg=<optimized out>) at /usr/include/c++/7/bits/unique_ptr.h:263
#5 0x0000555555679f01 in SkyMapComposite::~SkyMapComposite() (this=0x5555569548c0, __in_chrg=<optimized out>) at ./kstars/skycomponents/skymapcomposite.h:84
#6 0x000055555567e2c8 in SkyMapComposite::~SkyMapComposite() (this=0x5555569548c0, __in_chrg=<optimized out>) at ./kstars/skycomponents/skymapcomposite.h:84
#7 0x000055555567e2c8 in std::default_delete<SkyMapComposite>::operator()(SkyMapComposite*) const (this=<optimized out>, __ptr=0x5555569548c0) at /usr/include/c++/7/bits/unique_ptr.h:78
#8 0x000055555567e2c8 in std::unique_ptr<SkyMapComposite, std::default_delete<SkyMapComposite> >::~unique_ptr() (this=0x55555691ae18, __in_chrg=<optimized out>) at /usr/include/c++/7/bits/unique_ptr.h:263
#9 0x000055555567e2c8 in KStarsData::~KStarsData() (this=0x55555691ae00, __in_chrg=<optimized out>) at ./kstars/kstarsdata.cpp:119
#10 0x000055555567e4bd in KStarsData::~KStarsData() (this=0x55555691ae00, __in_chrg=<optimized out>) at ./kstars/kstarsdata.cpp:130
#11 0x000055555562c9a5 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at ./kstars/main.cpp:309

Thank you for the workaround, I will look into that as well.
Best,
Umair

On Jul 3 2020, at 1:25 pm, Akarsh Simha <akarshsimha at gmail.com> wrote:
> Hi Umair
>
> I don’t see the instructions you refer to. Could you give me the procedure you used? I’m not very familiar with valgrind either, but a backtrace from running under gdb should suffice. If you can tell me how you’re invoking it from the command line, I’ll look into it and see if I can reproduce the crash.
>
> Also: a workaround is to get the charts from the DBus interface when KStars is fully up and running.
>
> Regards
> Akarsh
>
>
> On Fri, Jul 3, 2020 at 10:19 Umair Khan <ukhan at pdx.edu (mailto:ukhan at pdx.edu)> wrote:
> > Hello,
> >
> > My name is Umair Khan, and I'm a student at Portland State University in Oregon. I'm not sure if this mailing list is a place to seek user support, so apologies if this is not the correct way to ask questions.
> > I'm trying to use KStars to generate images of the night sky from the command line, as per the instructions listed here. However, when I attempt to do so, the program segfaults with no error messages, and I'm not quite sure if or how this issue can be fixed. I was hoping someone here could provide some insight or a solution.
> > The GUI, on the other hand, works completely fine (at least as far as I can tell). Below are the details for the hardware I'm running KStars on:
> > OS: Ubuntu 18.04.4
> >
> > Kernel: 4.15.0-108-generic
> >
> > DE: GNOME 3.28.4
> >
> > CPU: Intel Core i7-6600u
> >
> >
> > In addition, I have attached two text files to this email containing shell input/output. One is for the plain command (default.txt), and another is a debug run using valgrind (valgrind.txt). Valgrind does appear to show several errors, but I am not quite sure how to interpret them or go about fixing them. Any help would be much appreciated.
> >
> > Thanks a lot for your consideration!
> > Best,
> > Umair
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20200703/d781f58b/attachment.htm>


More information about the Kstars-devel mailing list