bug-gnu-pspp
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PSPP-BUG: PSPP variable view seg fault ...


From: Maruthi Pathapati
Subject: Re: PSPP-BUG: PSPP variable view seg fault ...
Date: Sat, 28 Aug 2021 13:15:11 +0530

Hello John:

Greetings.

Thank you very much. I will pull the latest build.

Best Regards
Maruthi
CEO, Vidcentum
Phone: +91 9052512020




On Sat, Aug 28, 2021 at 12:52 PM John Darrington <john@darrington.wattle.id.au> wrote:
I have pushed a fix for this problem to git.

Thanks for reporting it.

Regards,

John

On Wed, Aug 04, 2021 at 05:32:57AM +0530, Maruthi Pathapati wrote:
     Hello John:

     Greetings.

     Thank you. I think I did not notice to report clicking on Name cell. My
     apologies. Anyway, the issue is known now.

     Best Regards
     Maruthi

     On Tue, Aug 3, 2021, 11:57 PM Ben Pfaff <blp@cs.stanford.edu> wrote:

     > I can reproduce this under valgrind, although between steps 4 and 5 I
     > have to click on the Name cell without entering anything. valgrind
     > prints the following additional information:
     >
     > ==624838== Invalid read of size 4
     > ==624838==    at 0x45E619: set_var_type (psppire-variable-sheet.c:52)
     > ==624838==    by 0x45EE9F: on_button_press (psppire-variable-sheet.c:561)
     > ==624838==    by 0x45EE9F: on_button_press (psppire-variable-sheet.c:555)
     > ==624838==    by 0x51CE326: ??? (in /usr/lib64/libgtk-3.so.0.2404.25)
     > ==624838==    by 0x594EC2E: g_closure_invoke (gclosure.c:810)
     > ==624838==    by 0x596AEA5: signal_emit_unlocked_R (gsignal.c:3741)
     > ==624838==    by 0x596C2DD: g_signal_emit_valist (gsignal.c:3507)
     > ==624838==    by 0x596C982: g_signal_emit (gsignal.c:3553)
     > ==624838==    by 0x5194F63: ??? (in /usr/lib64/libgtk-3.so.0.2404.25)
     > ==624838==    by 0x503831F: ??? (in /usr/lib64/libgtk-3.so.0.2404.25)
     > ==624838==    by 0x50391E9: gtk_main_do_event (in
     > /usr/lib64/libgtk-3.so.0.2404.25)
     > ==624838==    by 0x55D07D2: ??? (in /usr/lib64/libgdk-3.so.0.2404.25)
     > ==624838==    by 0x5607C15: ??? (in /usr/lib64/libgdk-3.so.0.2404.25)
     > ==624838==  Address 0x3c is not stack'd, malloc'd or (recently) free'd
     >
     > On Tue, Aug 3, 2021 at 3:18 AM Maruthi Pathapati <maruthi@vidcentum.com>
     > wrote:
     > >
     > > Hello John:
     > >
     > > I tried to get the stack trace of the crash.
     > >
     > > Thread 1 "psppire" received signal SIGSEGV, Segmentation fault.
     > > set_var_type (sheet=0x564849552120) at
     > src/ui/gui/psppire-variable-sheet.c:52
     > > 52  struct fmt_spec fmt = *format;
     > > (gdb) c
     > > Continuing.
     > > [Thread 0x7f6218ce5700 (LWP 91258) exited]
     > > (gdb)
     > >
     > > (gdb) bt
     > > #0  0x00007f621fe67aff in __GI___poll (fds=0x56484964d710, nfds=3,
     > timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
     > > #1  0x00007f622049636e in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
     > > #2  0x00007f62204966f3 in g_main_loop_run () at
     > /lib/x86_64-linux-gnu/libglib-2.0.so.0
     > > #3  0x00007f6220ab7497 in gtk_dialog_run () at
     > /lib/x86_64-linux-gnu/libgtk-3.so.0
     > > #4  0x000056484778a846 in fatal_error_handler (sig=11) at
     > src/ui/gui/main.c:397
     > > #5  0x00007f621ff593c0 in <signal handler called> () at
     > /lib/x86_64-linux-gnu/libpthread.so.0
     > > #6  set_var_type (sheet=0x564849552120) at
     > src/ui/gui/psppire-variable-sheet.c:52
     > > #7  0x00005648477ccee4 in on_button_press (w=<optimized out>,
     > e=<optimized out>, user_data=<optimized out>) at
     > src/ui/gui/psppire-variable-sheet.c:561
     > > #8  on_button_press (w=<optimized out>, e=<optimized out>,
     > user_data=<optimized out>) at src/ui/gui/psppire-variable-sheet.c:555
     > > #9  0x00007f6220ceb4fb in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
     > > #10 0x00007f6220581802 in g_closure_invoke () at
     > /lib/x86_64-linux-gnu/libgobject-2.0.so.0
     > > #11 0x00007f6220595814 in  () at
     > /lib/x86_64-linux-gnu/libgobject-2.0.so.0
     > > #12 0x00007f62205a047d in g_signal_emit_valist () at
     > /lib/x86_64-linux-gnu/libgobject-2.0.so.0
     > > #13 0x00007f62205a10f3 in g_signal_emit () at
     > /lib/x86_64-linux-gnu/libgobject-2.0.so.0
     > > #14 0x00007f6220c95c23 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
     > > #15 0x00007f6220b51128 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
     > > #16 0x00007f6220b533db in gtk_main_do_event () at
     > /lib/x86_64-linux-gnu/libgtk-3.so.0
     > > #17 0x00007f622083bf79 in  () at /lib/x86_64-linux-gnu/libgdk-3.so.0
     > > #18 0x00007f622086f106 in  () at /lib/x86_64-linux-gnu/libgdk-3.so.0
     > > #19 0x00007f622049617d in g_main_context_dispatch () at
     > /lib/x86_64-linux-gnu/libglib-2.0.so.0
     > > #20 0x00007f6220496400 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
     > > #21 0x00007f62204964a3 in g_main_context_iteration () at
     > /lib/x86_64-linux-gnu/libglib-2.0.so.0
     > > #22 0x00007f62206fefe5 in g_application_run () at
     > /lib/x86_64-linux-gnu/libgio-2.0.so.0
     > > #23 0x000056484778726b in main (argc=<optimized out>, argv=<optimized
     > out>) at src/ui/gui/main.c:560
     > >
     > >
     > > Hope that gives some idea.
     > >
     > >
     > > Best Regards
     > > Maruthi
     > > CEO, Vidcentum
     > > https://vidcentum.com
     > > Phone: +91 9052512020
     > > Skype: pvsmaruthi
     > >
     > >
     > >
     > > On Tue, Aug 3, 2021 at 12:52 PM John Darrington <
     > john@darrington.wattle.id.au> wrote:
     > >>
     > >> Hello  Maruthi,
     > >>
     > >> Thank you for the bug report.
     > >>
     > >> Unfortunately I haven't been able to reproduce this problem.
     > >>
     > >> Perhaps if you can generate a backtrace, then it might help shed
     > >> some light on this.
     > >>
     > >> Regards,
     > >>
     > >>
     > >> John
     > >>
     > >> On Tue, Aug 03, 2021 at 06:48:52AM +0530, Maruthi Pathapati wrote:
     > >>      Hello:
     > >>
     > >>      Greetings.
     > >>
     > >>      I was trying to use the latest test version of PSPP and learning
     > to extend
     > >>      it as required.
     > >>
     > >>      I found the following issue:
     > >>      proximate cause:    Segmentation Violation
     > >>      version:             GNU pspp 1.5.3-gee1bfc
     > >>      host_system:         x86_64-pc-linux-gnu
     > >>      build_system:        x86_64-pc-linux-gnu
     > >>      locale_dir:          /usr/local/share/locale
     > >>      compiler version:    9.3.0 (GCC)
     > >>
     > >>      OS: Ubuntu 20.04
     > >>      I have compiled spread-sheet-widget (0.8)
     > >>
     > >>      How to reproduce:
     > >>      1. Build the latest version (latest_source)
     > >>      2. Launch the PSPP GUI
     > >>      3. Go to Variable View (Data View and Variable Views are empty)
     > >>      4. Do not enter anything.
     > >>      5. "Double Click" on the "Type" cell. The Application throws a
     > segmentation
     > >>      error.
     > >>
     > >>      6. Open the GUI again
     > >>      7. Now fill  "Name" field
     > >>      8. Double click on the "Type" cell.  It works. It opens a pop-up
     > to select
     > >>      the type.
     > >>
     > >>      My observation: The issue may occur while launching Type dialog
     > when the
     > >>      cell is empty / uninitialized.
     > >>
     > >>      May I request you to look into the issue ?
     > >>
     > >>      Best Regards
     > >>      Maruthi
     > >>      CEO, Vidcentum
     > >>      https://vidcentum.com
     > >>      Phone: +91 9052512020
     > >>      Skype: pvsmaruthi
     > >>
     > >>      _______________________________________________
     > >>      Bug-gnu-pspp mailing list
     > >>      Bug-gnu-pspp@gnu.org
     > >>      https://lists.gnu.org/mailman/listinfo/bug-gnu-pspp
     > >>
     > > _______________________________________________
     > > Bug-gnu-pspp mailing list
     > > Bug-gnu-pspp@gnu.org
     > > https://lists.gnu.org/mailman/listinfo/bug-gnu-pspp
     >

reply via email to

[Prev in Thread] Current Thread [Next in Thread]