Wrong value returned when

Hi Julian,
since yesterday I have had several crashes of DB (GTK+ Unicode) when using the
copy shortcut. Until now I couldn't identify the sequence of actions which
leads to the crash.

Regards,
Thomas

--
Dipl.-Ing. Thomas Zehbe
INGENION GmbH
Kuhweide 6
31552 Apelern
Fon: 05043 / 40 57 90 4
Fax: 05043 / 40 57 90 7

Thomas Zehbe wrote:
> Hi Julian,
> since yesterday I have had several crashes of DB (GTK+ Unicode) when using the
> copy shortcut. Until now I couldn't identify the sequence of actions which
> leads to the crash.
>
Hi Thomas,

Unfortunately I can't reproduce this in the Elements sample on SuSE
Linux 9.2 with DB 3.06. I tried Ctrl-C in an element editor window and a
source editor window.

Regards,

Julian

Hi Julian,
Am Freitag, 25. August 2006 15:08 schrieb Julian Smart:
> Thomas Zehbe wrote:
> > Hi Julian,
> > since yesterday I have had several crashes of DB (GTK+ Unicode) when
> > using the copy shortcut. Until now I couldn't identify the sequence of
> > actions which leads to the crash.
>
> Hi Thomas,
>
> Unfortunately I can't reproduce this in the Elements sample on SuSE
> Linux 9.2 with DB 3.06. I tried Ctrl-C in an element editor window and a
> source editor window.
It happens occasionally without announcment. For now I start DB from the
command line window to capture the messages if it happens again.
Regards,

Thomas

>
> Regards,
>
> Julian
>
>
>
>
> Yahoo! Groups Links
>;
>
>

--
Dipl.-Ing. Thomas Zehbe
INGENION GmbH
Kuhweide 6
31552 Apelern
Fon: 05043 / 40 57 90 4
Fax: 05043 / 40 57 90 7

Hi Julian,
it just happend again. What did Leisure Suit Larry said?
Save early, save often ...
And I did.

Here's the output on the command line from the session:
tzluke:~/appdirs/eagle> dialogblocks

(dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion
`window != NULL' failed

(dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion
`window != NULL' failed

(dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion
`window != NULL' failed
[Debug] 15:06:07: Adding duplicate image handler for 'GIF file'
[Debug] 15:06:07: Adding duplicate image handler for 'PNG file'
[Debug] 15:06:07: Adding duplicate image handler for 'JPEG file'
[Debug] 15:06:07: Database connecting to:
[Debug] 15:06:07: PostgreSQL
[Debug] 15:55:06: Adding duplicate image handler for 'GIF file'
[Debug] 15:55:06: Adding duplicate image handler for 'PNG file'
[Debug] 15:55:06: Adding duplicate image handler for 'JPEG file'
[Debug] 15:55:06: Database connecting to:
[Debug] 15:55:06: PostgreSQL
[Debug] 16:12:56: Adding duplicate image handler for 'GIF file'
[Debug] 16:12:56: Adding duplicate image handler for 'PNG file'
[Debug] 16:12:56: Adding duplicate image handler for 'JPEG file'
[Debug] 16:12:56: Database connecting to:
[Debug] 16:12:56: PostgreSQL
*** glibc detected *** free(): invalid next size (fast): 0x0adade70 ***
/usr/local/bin/dialogblocks: line 4: 30816 Abgebrochen
$DIALOGBLOCKSDIR/dialogblocks $*
tzluke:~/appdirs/eagle>

The glibs is version 2.3.4-23 and it happend again when hitting ctrl-c in the
source code editor.

Regards,
Thomas

Am Freitag, 25. August 2006 15:54 schrieb Thomas Zehbe:
> Hi Julian,
>
> Am Freitag, 25. August 2006 15:08 schrieb Julian Smart:
> > Thomas Zehbe wrote:
> > > Hi Julian,
> > > since yesterday I have had several crashes of DB (GTK+ Unicode) when
> > > using the copy shortcut. Until now I couldn't identify the sequence of
> > > actions which leads to the crash.
> >
> > Hi Thomas,
> >
> > Unfortunately I can't reproduce this in the Elements sample on SuSE
> > Linux 9.2 with DB 3.06. I tried Ctrl-C in an element editor window and a
> > source editor window.
>
> It happens occasionally without announcment. For now I start DB from the
> command line window to capture the messages if it happens again.
> Regards,
>
> Thomas
>
> > Regards,
> >
> > Julian
> >
> >
> >
> >
> > Yahoo! Groups Links

--
Dipl.-Ing. Thomas Zehbe
INGENION GmbH
Kuhweide 6
31552 Apelern
Fon: 05043 / 40 57 90 4
Fax: 05043 / 40 57 90 7

Weird. And connecting to PostgreSQL too, I've no idea what that's about.
It's hard to know whether all those errors (apart from the 'free' one)
are completely unrelated to the problem, since you're showing all errors
since DB was run. If anyone else can replicate this Ctrl-C crash, it
would be interesting to know.

Thanks,

Julian

Thomas Zehbe wrote:
> Hi Julian,
> it just happend again. What did Leisure Suit Larry said?
>; Save early, save often ...
> And I did.
>
> Here's the output on the command line from the session:
> tzluke:~/appdirs/eagle> dialogblocks
>
> (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion
> `window != NULL' failed
>
> (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion
> `window != NULL' failed
>
> (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion
> `window != NULL' failed
> [Debug] 15:06:07: Adding duplicate image handler for 'GIF file'
>; [Debug] 15:06:07: Adding duplicate image handler for 'PNG file'
>; [Debug] 15:06:07: Adding duplicate image handler for 'JPEG file'
>; [Debug] 15:06:07: Database connecting to:
> [Debug] 15:06:07: PostgreSQL
> [Debug] 15:55:06: Adding duplicate image handler for 'GIF file'
>; [Debug] 15:55:06: Adding duplicate image handler for 'PNG file'
>; [Debug] 15:55:06: Adding duplicate image handler for 'JPEG file'
>; [Debug] 15:55:06: Database connecting to:
> [Debug] 15:55:06: PostgreSQL
> [Debug] 16:12:56: Adding duplicate image handler for 'GIF file'
>; [Debug] 16:12:56: Adding duplicate image handler for 'PNG file'
>; [Debug] 16:12:56: Adding duplicate image handler for 'JPEG file'
>; [Debug] 16:12:56: Database connecting to:
> [Debug] 16:12:56: PostgreSQL
> *** glibc detected *** free(): invalid next size (fast): 0x0adade70 ***
> /usr/local/bin/dialogblocks: line 4: 30816 Abgebrochen
> $DIALOGBLOCKSDIR/dialogblocks $*
> tzluke:~/appdirs/eagle>
>
> The glibs is version 2.3.4-23 and it happend again when hitting ctrl-c in the
> source code editor.
>
> Regards,
> Thomas
>
> Am Freitag, 25. August 2006 15:54 schrieb Thomas Zehbe:
>
>> Hi Julian,
>>
>> Am Freitag, 25. August 2006 15:08 schrieb Julian Smart:
>>
>>> Thomas Zehbe wrote:
>>>
>>>> Hi Julian,
>>>> since yesterday I have had several crashes of DB (GTK+ Unicode) when
>>>>; using the copy shortcut. Until now I couldn't identify the sequence of
>>>> actions which leads to the crash.
>>>>
>>> Hi Thomas,
>>>
>>> Unfortunately I can't reproduce this in the Elements sample on SuSE
>>> Linux 9.2 with DB 3.06. I tried Ctrl-C in an element editor window and a
>>;> source editor window.
>>>
>> It happens occasionally without announcment. For now I start DB from the
>> command line window to capture the messages if it happens again.
>> Regards,
>>
>> Thomas
>>
>;>
>>> Regards,
>>>;
>>> Julian
>>>
>>>
>>;>
>>>
>>> Yahoo! Groups Links
>;>>
>
>

--
Julian Smart, Anthemion Software Ltd.
28/5 Gillespie Crescent, Edinburgh, Midlothian, EH10 4HU
www.anthemion.co.uk | +44 (0)131 229 5306
Tools for writers: www.writerscafe.co.uk
wxWidgets RAD: www.anthemion.co.uk/dialogblocks

Am Freitag, 25. August 2006 16:54 schrieb Julian Smart:
> Weird. And connecting to PostgreSQL too, I've no idea what that's about.
> It's hard to know whether all those errors (apart from the 'free' one)
> are completely unrelated to the problem, since you're showing all errors
> since DB was run. If anyone else can replicate this Ctrl-C crash, it
> would be interesting to know.
Sorry, that I didn't mention that all the [Debug] lines are produced during
running my app by pressing F9. And the app connects to PostgreSQL.
Seems that DB catches stdout because that is the output I see when I start the
app from the command line.
All other ouput must be from DB. And the crash happened some time after the
last app run.

Regards,

Thomas

> Thanks,
>
> Julian
>
> Thomas Zehbe wrote:
> > Hi Julian,
> > it just happend again. What did Leisure Suit Larry said?
>; > Save early, save often ...
> > And I did.
> >
> > Here's the output on the command line from the session:
> > tzluke:~/appdirs/eagle> dialogblocks
> >
> > (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect:
> > assertion `window != NULL' failed
> >
> > (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect:
> > assertion `window != NULL' failed
> >
> > (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect:
> > assertion `window != NULL' failed
> > [Debug] 15:06:07: Adding duplicate image handler for 'GIF file'
>; > [Debug] 15:06:07: Adding duplicate image handler for 'PNG file'
>; > [Debug] 15:06:07: Adding duplicate image handler for 'JPEG file'
>; > [Debug] 15:06:07: Database connecting to:
> > [Debug] 15:06:07: PostgreSQL
> > [Debug] 15:55:06: Adding duplicate image handler for 'GIF file'
>; > [Debug] 15:55:06: Adding duplicate image handler for 'PNG file'
>; > [Debug] 15:55:06: Adding duplicate image handler for 'JPEG file'
>; > [Debug] 15:55:06: Database connecting to:
> > [Debug] 15:55:06: PostgreSQL
> > [Debug] 16:12:56: Adding duplicate image handler for 'GIF file'
>; > [Debug] 16:12:56: Adding duplicate image handler for 'PNG file'
>; > [Debug] 16:12:56: Adding duplicate image handler for 'JPEG file'
>; > [Debug] 16:12:56: Database connecting to:
> > [Debug] 16:12:56: PostgreSQL
> > *** glibc detected *** free(): invalid next size (fast): 0x0adade70 ***
> > /usr/local/bin/dialogblocks: line 4: 30816 Abgebrochen
> > $DIALOGBLOCKSDIR/dialogblocks $*
> > tzluke:~/appdirs/eagle>
> >
> > The glibs is version 2.3.4-23 and it happend again when hitting ctrl-c in
> > the source code editor.
> >
> > Regards,
> > Thomas
> >
> > Am Freitag, 25. August 2006 15:54 schrieb Thomas Zehbe:
> >> Hi Julian,
> >>
> >> Am Freitag, 25. August 2006 15:08 schrieb Julian Smart:
> >>> Thomas Zehbe wrote:
> >>>> Hi Julian,
> >>>> since yesterday I have had several crashes of DB (GTK+ Unicode) when
> >>>> using the copy shortcut. Until now I couldn't identify the sequence of
> >>>> actions which leads to the crash.
> >>>
> >>> Hi Thomas,
> >>>
> >>> Unfortunately I can't reproduce this in the Elements sample on SuSE
> >>> Linux 9.2 with DB 3.06. I tried Ctrl-C in an element editor window and
> >>> a source editor window.
> >>
> >> It happens occasionally without announcment. For now I start DB from the
> >> command line window to capture the messages if it happens again.
> >> Regards,
> >>
> >> Thomas
> >>
> >>> Regards,
> >>>
> >>> Julian
> >>>
> >>>
> >>>
> >>>
> >>> Yahoo! Groups Links

--
Dipl.-Ing. Thomas Zehbe
INGENION GmbH
Kuhweide 6
31552 Apelern
Fon: 05043 / 40 57 90 4
Fax: 05043 / 40 57 90 7

Hi Julian,
Maybe I'm a step closer to the crash problem. On my box I can now reproduce it
with a code snippet attached at these mail.
The crash happend after a very short DB usage period so that I could reproduce
all the "necessary steps."

It seems to be a charater count problem in the editor. Reproducing the bug on
my system works like this:
Copy the attachment to a convienient place. Open an arbitrary project and add
it to the "sources" part. After adding it you several line pairs of
SetColDefs().
Mark the two lines of one setcoldef statement either of the one containing
fzkmstand, fzpreisek or fzpreisvk. Start at the beginning of the first line
an mark until the cursor stands just at the beginning of the line with next
setcoldef. Then press ctrl+c and wait two tenth of a second. If you're lucky
(should be no joke) it crashes.

All three named entries have just the same length. I counterchecked my theory
by "tuning" another line pair to the same lenght. Just after the tuning,
ctrl+;c on this pair produces no crash, but with an intermediate ctrl+s on a
different part of the code the crash could be reproduced.

Hope this gives you a hint!
Regards,
Thomas

Am Freitag, 25. August 2006 16:54 schrieb Julian Smart:
> Weird. And connecting to PostgreSQL too, I've no idea what that's about.
> It's hard to know whether all those errors (apart from the 'free' one)
> are completely unrelated to the problem, since you're showing all errors
> since DB was run. If anyone else can replicate this Ctrl-C crash, it
> would be interesting to know.
>;
> Thanks,
>
> Julian
>
> Thomas Zehbe wrote:
> > Hi Julian,
> > it just happend again. What did Leisure Suit Larry said?
>; > Save early, save often ...
> > And I did.
> >
> > Here's the output on the command line from the session:
> > tzluke:~/appdirs/eagle> dialogblocks
> >
> > (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect:
> > assertion `window != NULL' failed
> >
> > (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect:
> > assertion `window != NULL' failed
> >
> > (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect:
> > assertion `window != NULL' failed
> > [Debug] 15:06:07: Adding duplicate image handler for 'GIF file'
>; > [Debug] 15:06:07: Adding duplicate image handler for 'PNG file'
>; > [Debug] 15:06:07: Adding duplicate image handler for 'JPEG file'
>; > [Debug] 15:06:07: Database connecting to:
> > [Debug] 15:06:07: PostgreSQL
> > [Debug] 15:55:06: Adding duplicate image handler for 'GIF file'
>; > [Debug] 15:55:06: Adding duplicate image handler for 'PNG file'
>; > [Debug] 15:55:06: Adding duplicate image handler for 'JPEG file'
>; > [Debug] 15:55:06: Database connecting to:
> > [Debug] 15:55:06: PostgreSQL
> > [Debug] 16:12:56: Adding duplicate image handler for 'GIF file'
>; > [Debug] 16:12:56: Adding duplicate image handler for 'PNG file'
>; > [Debug] 16:12:56: Adding duplicate image handler for 'JPEG file'
>; > [Debug] 16:12:56: Database connecting to:
> > [Debug] 16:12:56: PostgreSQL
> > *** glibc detected *** free(): invalid next size (fast): 0x0adade70 ***
> > /usr/local/bin/dialogblocks: line 4: 30816 Abgebrochen
> > $DIALOGBLOCKSDIR/dialogblocks $*
> > tzluke:~/appdirs/eagle>
> >
> > The glibs is version 2.3.4-23 and it happend again when hitting ctrl-c in
> > the source code editor.
> >
> > Regards,
> > Thomas
> >
> > Am Freitag, 25. August 2006 15:54 schrieb Thomas Zehbe:
> >> Hi Julian,
> >>
> >> Am Freitag, 25. August 2006 15:08 schrieb Julian Smart:
> >>> Thomas Zehbe wrote:
> >>>> Hi Julian,
> >>>> since yesterday I have had several crashes of DB (GTK+ Unicode) when
> >>>> using the copy shortcut. Until now I couldn't identify the sequence of
> >>>> actions which leads to the crash.
> >>>
> >>> Hi Thomas,
> >>>
> >>> Unfortunately I can't reproduce this in the Elements sample on SuSE
> >>> Linux 9.2 with DB 3.06. I tried Ctrl-C in an element editor window and
> >>> a source editor window.
> >>
> >> It happens occasionally without announcment. For now I start DB from the
> >> command line window to capture the messages if it happens again.
> >> Regards,
> >>
> >> Thomas
> >>
> >>> Regards,
> >>>
> >>> Julian
> >>>
> >>>
> >>>
> >>>
> >>> Yahoo! Groups Links

--
Dipl.-Ing. Thomas Zehbe
INGENION GmbH
Kuhweide 6
31552 Apelern
Fon: 05043 / 40 57 90 4
Fax: 05043 / 40 57 90 7

Hi Thomas,

Thanks, I've reproduced the crash using your file, and will investigate.

Regards,

Julian

Thomas Zehbe wrote:
> Hi Julian,
> Maybe I'm a step closer to the crash problem. On my box I can now reproduce it
> with a code snippet attached at these mail.
>; The crash happend after a very short DB usage period so that I could reproduce
> all the "necessary steps."
>
> It seems to be a charater count problem in the editor. Reproducing the bug on
> my system works like this:
>; Copy the attachment to a convienient place. Open an arbitrary project and add
> it to the "sources" part. After adding it you several line pairs of
> SetColDefs().
> Mark the two lines of one setcoldef statement either of the one containing
> fzkmstand, fzpreisek or fzpreisvk. Start at the beginning of the first line
> an mark until the cursor stands just at the beginning of the line with next
> setcoldef. Then press ctrl+c and wait two tenth of a second. If you're lucky
> (should be no joke) it crashes.
>
> All three named entries have just the same length. I counterchecked my theory
> by "tuning" another line pair to the same lenght. Just after the tuning,
> ctrl+c on this pair produces no crash, but with an intermediate ctrl+s on a
> different part of the code the crash could be reproduced.
>
> Hope this gives you a hint!
>; Regards,
> Thomas
>
> Am Freitag, 25. August 2006 16:54 schrieb Julian Smart:
>
>> Weird. And connecting to PostgreSQL too, I've no idea what that's about.
>> It's hard to know whether all those errors (apart from the 'free' one)
>> are completely unrelated to the problem, since you're showing all errors
>> since DB was run. If anyone else can replicate this Ctrl-C crash, it
>> would be interesting to know.
>;>
>> Thanks,
>>
>> Julian
>>
>;> Thomas Zehbe wrote:
>>
>>> Hi Julian,
>>> it just happend again. What did Leisure Suit Larry said?
>;>> Save early, save often ...
>>> And I did.
>>>
>>> Here's the output on the command line from the session:
>>>; tzluke:~/appdirs/eagle> dialogblocks
>>;>
>>> (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect:
>>> assertion `window != NULL' failed
>>>
>>> (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect:
>>> assertion `window != NULL' failed
>>>
>>> (dialogblocks:30816): Gdk-CRITICAL **: gdk_window_invalidate_rect:
>>> assertion `window != NULL' failed
>>> [Debug] 15:06:07: Adding duplicate image handler for 'GIF file'
>;>> [Debug] 15:06:07: Adding duplicate image handler for 'PNG file'
>;>> [Debug] 15:06:07: Adding duplicate image handler for 'JPEG file'
>;>> [Debug] 15:06:07: Database connecting to:
>>> [Debug] 15:06:07: PostgreSQL
>>> [Debug] 15:55:06: Adding duplicate image handler for 'GIF file'
>;>> [Debug] 15:55:06: Adding duplicate image handler for 'PNG file'
>;>> [Debug] 15:55:06: Adding duplicate image handler for 'JPEG file'
>;>> [Debug] 15:55:06: Database connecting to:
>>> [Debug] 15:55:06: PostgreSQL
>>> [Debug] 16:12:56: Adding duplicate image handler for 'GIF file'
>;>> [Debug] 16:12:56: Adding duplicate image handler for 'PNG file'
>;>> [Debug] 16:12:56: Adding duplicate image handler for 'JPEG file'
>;>> [Debug] 16:12:56: Database connecting to:
>>> [Debug] 16:12:56: PostgreSQL
>>> *** glibc detected *** free(): invalid next size (fast): 0x0adade70 ***
>>> /usr/local/bin/dialogblocks: line 4: 30816 Abgebrochen
>>> $DIALOGBLOCKSDIR/dialogblocks $*
>>> tzluke:~/appdirs/eagle>
>>>
>>> The glibs is version 2.3.4-23 and it happend again when hitting ctrl-c in
>>> the source code editor.
>>>
>>> Regards,
>>>; Thomas
>>>
>>> Am Freitag, 25. August 2006 15:54 schrieb Thomas Zehbe:
>>>
>>>> Hi Julian,
>>>>
>>>> Am Freitag, 25. August 2006 15:08 schrieb Julian Smart:
>>>>
>>>>>; Thomas Zehbe wrote:
>>>>>
>>>>>;> Hi Julian,
>>>>>>; since yesterday I have had several crashes of DB (GTK+ Unicode) when
>>>>;>> using the copy shortcut. Until now I couldn't identify the sequence of
>>>>>> actions which leads to the crash.
>>>>>>
>>>>>; Hi Thomas,
>>>>>
>>>>> Unfortunately I can't reproduce this in the Elements sample on SuSE
>>>>;> Linux 9.2 with DB 3.06. I tried Ctrl-C in an element editor window and
>>>>> a source editor window.
>>>>>
>>>> It happens occasionally without announcment. For now I start DB from the
>>>> command line window to capture the messages if it happens again.
>>>> Regards,
>>>;>
>>>>; Thomas
>>>>
>>>>
>>>>>; Regards,
>>>;>>
>>>;>> Julian
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Yahoo! Groups Links
>;>>>>
>
>

--
Julian Smart, Anthemion Software Ltd.
28/5 Gillespie Crescent, Edinburgh, Midlothian, EH10 4HU
www.anthemion.co.uk | +44 (0)131 229 5306
Tools for writers: www.writerscafe.co.uk
wxWidgets RAD: www.anthemion.co.uk/dialogblocks

Thomas,

Which Linux version of DB are you using (e.g. SuSE 9.2-compiled)? I've
built DB against current wxWidgets CVS 2.6 and it seems not to be
segfaulting; perhaps I could ask you to try it out.

Thanks,

Julian