Your message dated Sat, 8 Dec 2018 08:48:54 +0100
with message-id <[email protected]>
and subject line segfaults when importing csv file in g_date_time_to_unix 
(datetime=datetime@entry=0x0)
has caused the Debian Bug report #855511,
regarding segfaults when importing csv file in g_date_time_to_unix 
(datetime=datetime@entry=0x0)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
855511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855511
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnucash
Version: 1:2.6.15-1
Severity: normal

Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault.
g_date_time_to_unix (datetime=datetime@entry=0x0) at ././glib/gdatetime.c:1900
1900    ././glib/gdatetime.c: No such file or directory.
(gdb) bt
#0  0x00007ffff5f76034 in g_date_time_to_unix (datetime=datetime@entry=0x0) at 
././glib/gdatetime.c:1900
#1  0x00007ffff6ca2b5b in gnc_dmy2timespec_neutral (day=day@entry=2017, 
month=month@entry=17, year=year@entry=2002)
    at gnc-date.c:1590
#2  0x00007fffdc9fae01 in parse_date_with_year (format=<optimized out>, 
date_str=0x5555585b3ca0 "02/17/2017")
    at gnc-csv-model.c:203
#3  0x00007fffdc9fae01 in parse_date (date_str=0x5555585b3ca0 "02/17/2017", 
format=0) at gnc-csv-model.c:295
#4  0x00007fffdc9f86a3 in preview_settings_valid 
(info=info@entry=0x5555584abcf0) at assistant-csv-trans-import.c:1052
#5  0x00007fffdc9f8a01 in csv_import_trans_assistant_account_page_prepare 
(assistant=0x5555584182a0 [GtkAssistant], user_data=0x5555584abcf0) at 
assistant-csv-trans-import.c:1424
#9  0x00007ffff3a2ffaf in <emit signal ??? on instance 0x5555584182a0 
[GtkAssistant]> (instance=<optimized out>, signal_id=<optimized out>, 
detail=<optimized out>) at ././gobject/gsignal.c:3447
    #6  0x00007ffff3a14f75 in g_closure_invoke (closure=0x5555584d41c0, 
return_value=return_value@entry=0x0, n_param_values=2, 
param_values=param_values@entry=0x7fffffffb790, 
invocation_hint=invocation_hint@entry=0x7fffffffb710)
    at ././gobject/gclosure.c:804
    #7  0x00007ffff3a26f82 in signal_emit_unlocked_R 
(node=node@entry=0x555558416ac0, detail=detail@entry=0, 
instance=instance@entry=0x5555584182a0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffffffb790) at 
././gobject/gsignal.c:3635
    #8  0x00007ffff3a2fbcc in g_signal_emit_valist (instance=<optimized out>, 
signal_id=<optimized out>, detail=<optimized out>, 
var_args=var_args@entry=0x7fffffffb950) at ././gobject/gsignal.c:3391
#10 0x00007ffff62d36f7 in  () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0


so the invocation is in

1589        GDateTime *gdt = gnc_g_date_time_new_local (year, month, day, 10, 
59, 0.0);
1590        int interval = g_time_zone_find_interval (zone, 
G_TIME_TYPE_STANDARD,
1591                                                  g_date_time_to_unix(gdt));


and gdt is null

(gdb) p gdt
$5 = (GDateTime *) 0x0

and that is due to me forgetting to specify correct date format

(gdb) p year
$6 = 2002
(gdb) p month
$7 = 17
(gdb) p day
$8 = 2017

which when I specified correctly imported fine ;)  so it would be nice if some
basic analysis, e.g. checking here for null could be performed and some
informative message was issued instead of segfaulting


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnucash depends on:
ii  gnucash-common             1:2.6.15-1
ii  guile-2.0                  2.0.13+1-4
ii  guile-2.0-libs             2.0.13+1-4
ii  libaqbanking35             5.6.12-1
ii  libaqbanking35-plugins     5.6.12-1
ii  libc6                      2.24-9
ii  libcairo2                  1.14.8-1
ii  libcrypt-ssleay-perl       0.73.04-1+b3
ii  libdate-manip-perl         6.57-1
ii  libdbi1                    0.9.0-4
ii  libfinance-quote-perl      1.38-1
ii  libgdk-pixbuf2.0-0         2.36.4-1
ii  libglib2.0-0               2.50.2-2
ii  libgnome-keyring0          3.12.0-1+b1
ii  libgnomecanvas2-0          2.30.3-3
ii  libgoffice-0.8-8           0.8.17-7
ii  libgtk2.0-0                2.24.31-2
ii  libgwengui-gtk2-0          4.15.3-5
ii  libgwenhywfar60            4.15.3-5
ii  libhtml-tableextract-perl  2.13-1
ii  libhtml-tree-perl          5.03-2
ii  libktoblzcheck1v5          1.48-2.1
ii  libofx6                    1:0.9.10-2
ii  libpango-1.0-0             1.40.3-3
ii  libpangocairo-1.0-0        1.40.3-3
ii  libpython2.7               2.7.13-2
ii  libwebkitgtk-1.0-0         2.4.11-3
ii  libwww-perl                6.15-1
ii  libx11-6                   2:1.6.4-3
ii  libxml2                    2.9.4+dfsg1-2.2
ii  libxslt1.1                 1.1.29-2
pn  perl:any                   <none>
ii  zlib1g                     1:1.2.8.dfsg-5

Versions of packages gnucash recommends:
ii  dbus            1.10.14-1
ii  dbus-x11        1.10.14-1
ii  gnucash-docs    2.6.15-1
ii  python-gnucash  1:2.6.15-1
ii  yelp            3.22.0-1

Versions of packages gnucash suggests:
pn  libdbd-mysql    <none>
pn  libdbd-pgsql    <none>
pn  libdbd-sqlite3  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
forwarded 855511 https://bugs.gnucash.org/show_bug.cgi?id=778112
fixed 855511 1:3.0-1
thanks

--- End Message ---

Reply via email to