fer a donation via Gnucash SEPA transfer to Geert Jaansens
account failed somehow. I will use the Browser for now and look into that issue
tommorrow.
Best wishes to all of you
have a great day
Alex
PS. tax export still crashing giving segmentation fault error.
On Tue, 15 Oct 2019 06:08:29 -0400
&
uts … ]
>
> Gnucash is open. Empty file. I enter the aqbanking wizard straight away,
> "edit" the only existing user, "get certificate", OK, "Get Bank Info", Crash.
>
> Here's the first lines of the backtrace:
>
> Thread 1 "gn
away,
> "edit" the only existing user, "get certificate", OK, "Get Bank Info",
> Crash.
>
> Here's the first lines of the backtrace:
>
> Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault.
> 0x7fffd6283989 in GWE
ugging outputs … ]
>
> Gnucash is open. Empty file. I enter the aqbanking wizard straight
> away, "edit" the only existing user, "get certificate", OK, "Get
> Bank Info", Crash.
>
> Here's the first lines of the backtrace:
>
> Thread
t"
the only existing user, "get certificate", OK, "Get Bank Info", Crash.
Here's the first lines of the backtrace:
Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault.
0x7fffd6283989 in GWEN_Text_EscapeToBuffer ()
from /usr/lib/x86_64-linux-gn
> On Oct 14, 2019, at 2:51 PM, Martin Preuss wrote:
>
> Hi,
>
> Am 14.10.19 um 21:51 schrieb Christian Stimming:
> [...]
>>> (gdb) bt full
>>> #0 0x7fffd6075989 in GWEN_Text_EscapeToBuffer ()
>>>at /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60
>>> #1 0x7fffbe22d5a3 in GWEN_Confi
Hi,
Am 14.10.19 um 21:51 schrieb Christian Stimming:
[...]
>> (gdb) bt full
>> #0 0x7fffd6075989 in GWEN_Text_EscapeToBuffer ()
>> at /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60
>> #1 0x7fffbe22d5a3 in GWEN_ConfigMgrDir_AddGroupFileName ()
>> at /usr/lib/x86_64-linux-gnu/gwenhy
can do anything else.
>
> -- GDB BACKTRACE START ---
>
> Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault.
> 0x7fffd6075989 in GWEN_Text_EscapeToBuffer ()
>from /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60
> (gdb) bt full
> #0 0x7fffd6
Here is a backtrace of Gnucash when crashing upon clicking on "Get Bank Info"
in the aqbanking wizard. Let me know if I can do anything else.
-- GDB BACKTRACE START ---
Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault.
0x7fffd6075989 in GWEN_Text_EscapeToBu
Alex wrote:
> Hi Derek,
> thanks for looking into it.
> Here is a backtrace of Gnucash when crashing upon clicking on "Get Bank
> Info" in the aqbanking wizard. Let me know if I can do anything else.
>
> -- GDB BACKTRACE START ---
>
> Thread 1 "gnucash&
How about a GDB Backtrace?
-derek
On Mon, October 14, 2019 11:01 am, Alex wrote:
> May anyone help me and others resolving this issue?
>
> Gnucash crashes upon online-actions with "segmentation fault" and maybe
> other errors (see log / trace excerpts below).
>
>
May anyone help me and others resolving this issue?
Gnucash crashes upon online-actions with "segmentation fault" and maybe other
errors (see log / trace excerpts below).
I had compiled and installed gwenhywfar (./configure --with-guis="gtk3") and
aqbanking bleeding edge
t;>
>> Modified:
>> gnucash/trunk/src/register/ledger-core/split-register-model.c
>> Log:
>> Bug 721791 - Segmentation fault when correcting invalid date
>>
>> And greatly simplify gnc_split_register_get_date_help by just getting a
>> GDate and ru
-model.c
> Log:
> Bug 721791 - Segmentation fault when correcting invalid date
>
> And greatly simplify gnc_split_register_get_date_help by just getting a
> GDate and running g_date_strftime on it instead of messing around with
> Timespecs and g_localtime_r (twice!) and all of that
On Dec 2, 2013, at 2:13 PM, Herbert Mühlburger wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am 02.12.13 18:18, schrieb John Ralls:
>> At this point I think you should open a bug report.
>
> I created the bug https://bugzilla.gnome.org/show_bug.cgi?id=719726
> regarding this i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 02.12.13 18:18, schrieb John Ralls:
> At this point I think you should open a bug report.
I created the bug https://bugzilla.gnome.org/show_bug.cgi?id=719726
regarding this issue. Do you have any idea where the problem could be?
Kind regards,
He
On Dec 2, 2013, at 8:47 AM, Herbert Mühlburger wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am 02.12.13 16:55, schrieb John Ralls:
>>
>>> That's a very strange crash.
>>
>>> I don't see it, but I'm got other weird behavior, where none of
>>> the GUI buttons, checkboxes, or G
Christian,
On Sun, Mar 25, 2012 at 12:15 PM, Christian Stimming
wrote:
> Am Samstag, 24. März 2012, 17:38:31 schrieb Alex Aycinena:
>> Christian,
>>
>> I built a clean copy of trunk on r22118 and got a seg fault on start
>> up as follows:
>>
>> Program rece
Am Samstag, 24. März 2012, 17:38:31 schrieb Alex Aycinena:
> Christian,
>
> I built a clean copy of trunk on r22118 and got a seg fault on start
> up as follows:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x7792b31c in gnc_split_register_load
Christian,
I built a clean copy of trunk on r22118 and got a seg fault on start
up as follows:
Program received signal SIGSEGV, Segmentation fault.
0x7792b31c in gnc_split_register_load (reg=0x7f2980, slist=
0xd04a20 = {...}, default_account=0xb943f0)
at
/home/gnucash-dev
bin-Message: main: binreloc relocation support was disabled at configure
time.
[New Thread 0x808202f00 (LWP 100133)]
Found Finance::Quote version 1.15
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x808202180 (LWP 100211)]
0x000800c0e28f in set_dimensions_pass_one (she
a file, which opened with only the
> > accounts window, the program crashed when I selected an account (
> > or would have if I had'nt had gdb running).
> >
> > And the backtrace follows.
> >
> > Dave
> >
> >
> > Program received signal
d'nt had gdb running).
>
> And the backtrace follows.
>
> Dave
>
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x808202180 (LWP 100211)]
> 0x000800c0e28f in set_dimensions_pass_one (sheet=0x80be18060,
> cursor=0x808256700, dimen
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
Am Wednesday 22 April 2009 06:11:34 schrieben Sie:
>On Tue, Apr 21, 2009 at 01:56:44PM +0200, Sebastian Held wrote:
>> >Program received signal SIGSEGV,
>Program received signal SIGSEGV, Segmentation fault.
>[Switching to Thread 0x808102180 (LWP 100227)]
>gnucash_sheet_styles_set_dimensions (sheet=0x80bd340c0, default_width=680)
>at gnucash-style.c:177
>177gnucash-style.c: No such file or directory.
> in gnucash
age: main: binreloc relocation support was disabled at
> configure time.
>
> Found Finance::Quote version 1.15
> [1]93890 segmentation fault gnucash --debug --extra
>
>
> Extracts from gnucash.trace
>
> * 15:44:13 INFO [gnc_hook_lookup] no hook lists
> * 15:44:13
it on IRC. Chris reports -- and
I can verify -- it's fixed in r13378.
gnucash --nofile
just gave me a segmentation fault on 13378.
Can you post the top 10 frames of the stack trace?
David
Here is the complete stack trace:
Program received signal SIGSEGV, Se
IRC. Chris reports -- and
> > I can verify -- it's fixed in r13378.
> >
> >
> gnucash --nofile
> just gave me a segmentation fault on 13378.
Can you post the top 10 frames of the stack trace?
David
___
gnucash-devel mai
Josh Sled wrote:
On Thu, 2006-02-23 at 20:28 -0700, Mark Johnson wrote:
With gnucash svn 13366, I am getting a segmentation fault for the
command line:
$ gnucash --nofile
This is repeatable. I was trying this because it was crashing when I
tried File->New->new file with
On Thu, 2006-02-23 at 20:28 -0700, Mark Johnson wrote:
> With gnucash svn 13366, I am getting a segmentation fault for the
> command line:
> $ gnucash --nofile
>
> This is repeatable. I was trying this because it was crashing when I
> tried File->New->new file with a fi
With gnucash svn 13366, I am getting a segmentation fault for the
command line:
$ gnucash --nofile
This is repeatable. I was trying this because it was crashing when I
tried File->New->new file with a file open. That crash was also repeatable.
Any one else seeing this? Is it fixe
me a segmentation fault
on launch. Since no one else has been complaining, I figured it
must be me, but I'm looking for suggestions.
the guile crash log starts out:
Host Name: G5D
Date/Time: 2005-11-23 18:40:19.481 -0500
OS Version: 10.4.3 (Build 8F46)
Report Version: 3
Command:
r12021 and at least a couple earlier give me a segmentation fault on
launch. Since no one else has been complaining, I figured it must be
me, but I'm looking for suggestions.
the guile crash log starts out:
Host Name: G5D
Date/Time: 2005-11-23 18:40:19.481 -0500
OS Ve
Quoting Matthew Vanecek <[EMAIL PROTECTED]>:
> I'm kinda skeptical about using the contents of a freed Split to see if
> the Split has been freed, though. What if something else has
> overwritten the freed memory? Why is that particular pointer guaranteed
> to still be == (char *)1 if the split
Quoting Thomas Bushnell BSG <[EMAIL PROTECTED]>:
> Derek Atkins <[EMAIL PROTECTED]> writes:
>
> > And yes, this code has been there a long time, in order to detect a
> > double-free.
>
> That's a bug then; you can't access freed memory, period.
Well, yes and no...
> Indeed, it is fair game
On Fri, 2005-01-21 at 21:09 -0600, Matthew Vanecek wrote:
> On Fri, 2005-01-21 at 11:37 -0800, Thomas Bushnell BSG wrote:
> > Derek Atkins <[EMAIL PROTECTED]> writes:
[snip]
> It's faulting on my P3 nowadays for some reason. I wasn't sure if it
> was a glibc thing or what. Quite annoying. I w
Derek Atkins <[EMAIL PROTECTED]> writes:
> And yes, this code has been there a long time, in order to detect a
> double-free.
That's a bug then; you can't access freed memory, period.
Indeed, it is fair game for an attempted read out of freed memory to
fault; it's been freed, you can't read
On Fri, 2005-01-21 at 11:37 -0800, Thomas Bushnell BSG wrote:
> Derek Atkins <[EMAIL PROTECTED]> writes:
>
> > I see nothing wrong with this code. It should be perfectly legal to
> > set an invalid pointer like this. Unless you are specifically doing
> > bounds-checking on pointer-sets I can't s
Derek Atkins <[EMAIL PROTECTED]> writes:
> I see nothing wrong with this code. It should be perfectly legal to
> set an invalid pointer like this. Unless you are specifically doing
> bounds-checking on pointer-sets I can't see how setting a pointer
> would cause a SEGV. You're not ACCESSING the
d***";
And then use 'deleted_string' instead of "(char *) 1"..
-derek
"Matthew Vanecek" <[EMAIL PROTECTED]> writes:
> hey,
> I don't know if this is just my machine, or what, but I've started getting
> a segmentation fault in Gnucash, gnuc
hey,
I don't know if this is just my machine, or what, but I've started getting
a segmentation fault in Gnucash, gnucash-gnome2-dev branch. I'm running
Fedora Core 3, updated via up2date somewhat regularly. The crash occurs
when loading an existing file, or when exiting after crea
41 matches
Mail list logo
