Linas,
These messages have always been in stdout (or stderr) for me... is my
configuration somehow different? I haven't tried recently so I don't
know if it's changed for me recently or not. But I've never noticed
/tmp/gnucash.trace before.
-derek
[EMAIL PROTECTED] (Linas Vepstas) writes:
>
On Mon, Aug 16, 2004 at 11:39:02PM +0100, Neil Williams was heard to remark:
> On Monday 16 August 2004 10:48, Linas Vepstas wrote:
> > > (Doesn't look right to me).
> >
> > What doesn't look right?
>
> Documentation?
For what?
> This caught me by surprise and I spent a little time (with
? Th
On Monday 16 August 2004 10:48, Linas Vepstas wrote:
> > (Doesn't look right to me).
>
> What doesn't look right?
Documentation? This caught me by surprise and I spent a little time (with
Derek in this thread) investigating when that time could have been useful on
something else. I was trucking
On Mon, Aug 16, 2004 at 10:16:10PM +0100, Neil Williams was heard to remark:
> On Monday 16 August 2004 8:22, Linas Vepstas wrote:
> > > As is, that is completely silent, no message at all.
> >
> > Make sure that the code in src/engine/gnc-trace.c isn't dumping all
> > messages to a logfile (e.g. /
On Monday 16 August 2004 8:22, Linas Vepstas wrote:
> > As is, that is completely silent, no message at all.
>
> Make sure that the code in src/engine/gnc-trace.c isn't dumping all
> messages to a logfile (e.g. /tmp/gnucash.trace or something like that).
Aha! Thanks Linas!
Was this intended?
Diff
race.c isn't dumping all
messages to a logfile (e.g. /tmp/gnucash.trace or something like that).
--linas
>
> Uncomment the first g_return and the message appears.
> ** CRITICAL **: file example-gncBookMerge.c: line 158 (main): assertion `(1 ==
> 2)' failed.
>
--
MAIN.
neiltest-CRITICAL **: file neiltest.c line 19 (main): assertion `(1 == 2)'
failed
Note that the second g_message (engine init done) does not print but as soon
as G_LOG_DOMAIN is redefined, the next g_message does print (engine has shut
down) and the g_return assert does display the c
ndefining
G_DISABLE_CHECKS had no effect, with or without G_LOG_DOMAIN.
It was a test program that shows the effect best. g_message and g_return...
work as expected before gnc_engine_init is called. After that, they are
silent. Only by setting the log domain are the calls executed properly.
e.
Very odd... I don't see why this should be required. We never
set G_LOG_DOMAIN anywhere in our code, and it's always worked just
fine. Is something, somehow, setting G_DISABLE_CHECKS?
-derek
Neil Williams <[EMAIL PROTECTED]> writes:
> On Thursday 12 August 2004 12:03, Neil Williams wrote:
>>
On Thursday 12 August 2004 12:03, Neil Williams wrote:
> On Wednesday 11 August 2004 10:33, Derek Atkins wrote:
> > Neil Williams <[EMAIL PROTECTED]> writes:
> > > I even tried g_return_if_fail(1 == 2);
> >
> > This should definitely trigger...
This is what I needed to solve the problem:
in my .c
fail((1 == 2), 55);
As is, that is completely silent, no message at all.
Uncomment the first g_return and the message appears.
** CRITICAL **: file example-gncBookMerge.c: line 158 (main): assertion `(1 ==
2)' failed.
I'm going to rebuild from a pristine CVS tree on Friday (v.busy d
Neil Williams <[EMAIL PROTECTED]> writes:
> I even tried g_return_if_fail(1 == 2);
This should definitely trigger...
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/
On Wednesday 11 August 2004 7:25, Derek Atkins wrote:
> I'll also note that in the snippet you sent,
> qof_book_mergeUpdateResult() doesn't return anything, so you don't
> even get an error code back. Not sure how what it's updating, or how
> "remainder" gets changed.. :)
the g_return_if_fail is
Well, for one thing, it's possible to turn off the g_return functions..
Take a look at glib.h and see. If you have the right stuff defined
it will ignore the functions completely. You may have set that.
I'll also note that in the snippet you sent,
qof_book_mergeUpdateResult() does
On Wednesday 11 August 2004 5:44, Derek Atkins wrote:
> Uh, show me the code that's failing?
I'm using g_return_if_fail in lots of areas and it used to work - because it's
all over the source, I put the URL in the message:
> > http://www.codehelp.co.uk/code/source.html
A
Uh, show me the code that's failing?
I don't THINK you need anything special to get it to print a
warning... But honestly I'm not 100% sure.
-derek
Neil Williams <[EMAIL PROTECTED]> writes:
> Can someone help me find out why my g_return statements are no longer pri
Can someone help me find out why my g_return statements are no longer printing
messages to the terminal?
I'm getting errors from the rest of GnuCash (if I force the error, it tests OK
otherwise) but when I'm testing my merge code (deliberately trying to
generate errors), I'm
17 matches
Mail list logo
