Martin Vermeer wrote:
>> ps, see if you can trigger the bug with current cvs. Also the math one...
>
> Yes, the bug is gone. So is the math bug.
Good news indeed.
> These kind of bugs based upon unspecified compiler behaviour are hell
> to hunt down. I think we did our good deed for this week!
On Thu, Sep 18, 2003 at 12:57:40PM +, Angus Leeming spake thusly:
> On Thursday 18 September 2003 11:58 am, Martin Vermeer wrote:
> > > your patch and apply mine. Yours is a work around broken behaviour.
> > > Mine cures the source of the breakage.
> >
> > I very much agree -- provided it work
On Thursday 18 September 2003 11:58 am, Martin Vermeer wrote:
> > your patch and apply mine. Yours is a work around broken behaviour.
> > Mine cures the source of the breakage.
>
> I very much agree -- provided it works. (Do you mean the dialogs.diff
> patch you posted here much earlier? But you ca
On Thu, Sep 18, 2003 at 09:05:57AM +, Angus Leeming spake thusly:
> Martin Vermeer wrote:
> > Here's the patch.
>
> And I understand how it is triggered. We have a sort of 'race'
> condition between the destruction of two static variables.
>
> In gettext.C:
> Messages & getLyXMessages() {
On Thu, Sep 18, 2003 at 09:45:06AM +, Angus Leeming wrote:
> Andre Poenitz wrote:
> > As the destruction order is the reversed construction order you
> > could specify a certain order if you need to.
>
> Let's just not go there in the first place.
Fine with me.
Andre'
Andre Poenitz wrote:
> As the destruction order is the reversed construction order you
> could specify a certain order if you need to.
Let's just not go there in the first place.
--
Angus
On Thu, Sep 18, 2003 at 09:25:41AM +, Angus Leeming wrote:
> Alfredo Braunstein wrote:
>
> > Martin Vermeer wrote:
> >
> >> 3) I discovered a new (?) bug:
> >>
> >> a) create an inset, e.g., note;
> >> b) insert a math inset into it;
> >> c) copy and paste the math inset to inside the note i
Alfredo Braunstein wrote:
> Martin Vermeer wrote:
>
>> 3) I discovered a new (?) bug:
>>
>> a) create an inset, e.g., note;
>> b) insert a math inset into it;
>> c) copy and paste the math inset to inside the note inset;
>> d) exit without saving.
>
> I don't see it.
No, it's going to be a com
Martin Vermeer wrote:
> Here's the patch.
And I understand how it is triggered. We have a sort of 'race'
condition between the destruction of two static variables.
In gettext.C:
Messages & getLyXMessages() {
static Messages lyx_messages;
return lyx_messages;
}
In Dialogs.C
names
Martin Vermeer wrote:
> 3) I discovered a new (?) bug:
>
> a) create an inset, e.g., note;
> b) insert a math inset into it;
> c) copy and paste the math inset to inside the note inset;
> d) exit without saving.
I don't see it.
Alfredo
On Wed, Sep 17, 2003 at 06:35:10PM +0100, Angus Leeming spake thusly:
>
> Martin Vermeer wrote:
> > Yes! This does the trick.
>
> Great! I wonder what changed between 13x and 14x in this regard.
>
> > Shall I prepare a patch?
>
> Why not.
Here's the patch.
Notes:
1) To suppress the bug, it w
Looking deeper, LOCALEDIR should be ${INSTALL_DIR}/share/locale I
think
Angus
| Install locally. Something like this should do the trick.
| Note that the important line is the penultimate one.
| See main.C and thereafter the code in ${LYX_TOP_DIR}/intl
| $ INSTALL_DIR=/home/martin/lyx/test-i
Martin Vermeer wrote:
> Yes! This does the trick.
Great! I wonder what changed between 13x and 14x in this regard.
> Shall I prepare a patch?
Why not.
>> > By the way, I run CVS LyX uninstalled. Relevant?
>> Not to the fact that the code is crashing, no.
> What I don't like though is that lo
On Wed, Sep 17, 2003 at 04:32:50PM +0100, Angus Leeming spake thusly:
...
> or alternatively:
> void FormDialogView::prepare_to_show()
> {
> ...
> if (!lyxrc.dialogs_iconify_with_main)
> - fl_winicontitle(form()->window, getTitle().c_str());
> + fl_win
Angus Leeming wrote:
> Incidentally, maybe a script would help automate the changing of
> those _("Minipage settings") to N_(...)
>
> for file in Form*.C; do
> sed 's/\(^[ ]*: base_class([^_]*\)_/\1N_/' $file > tmp
> cmp -s $file tmp && continue
> diff -u $file tmp
> mv -i tmp $file
> done
Martin Vermeer wrote:
>> or presumably alternatively:
>>
>> // file frontends/xforms/xformsBC.C
>> void xformsBC::setButtonLabel(FL_OBJECT * obj, string const &
>> label) const
>> {
>> fl_set_object_label(obj, _(label).c_str());
>> }
>
> Yes! This bites. At least for Cancel and Close.
>
On Wed, Sep 17, 2003 at 02:53:27PM +0100, Angus Leeming spake thusly:
> Martin Vermeer wrote:
> > Yes, I know how gettext works -- I did the first Dutch and Finnish
> > translations remember? But I still don't get what Lars wanted
> > me to do. Please bend it in copperwire for me. Remember I'm a
Martin Vermeer wrote:
> Yes, I know how gettext works -- I did the first Dutch and Finnish
> translations remember? But I still don't get what Lars wanted
> me to do. Please bend it in copperwire for me. Remember I'm a little
> dumb :-)
My misunderstanding.
Ok, I think that Lars is suggesting
//
On Wed, Sep 17, 2003 at 02:15:35PM +0100, Angus Leeming spake thusly:
>
> Martin Vermeer wrote:
...
> >
> > Like this?
>
> No, because this is code executed when the xformsBC constructor is
> invoked.
> xformsBC(ButtonController const &,
> -string const & = _("Cancel"), strin
Martin Vermeer wrote:
> On Wed, Sep 17, 2003 at 11:28:36AM +0100, Angus Leeming spake
thusly:
>
>> Martin Vermeer wrote:
>>
>> > On Wed, Sep 17, 2003 at 10:52:48AM +0200, Lars Gullik Bjønnes
spake
>> > thusly:
>> >
>> >> what happens if you function call replace the default args with
>> >>
On Wed, Sep 17, 2003 at 10:52:48AM +0200, Lars Gullik Bjønnes spake thusly:
...
> Or remove the _(..) from the default args completely?
>
> --
> Lgb
Yes, then the error goes away. But do we want that? We want "Cancel"
and "Close" translated, don't we?
- Martin
pgp0.pgp
Descrip
On Wed, Sep 17, 2003 at 11:28:36AM +0100, Angus Leeming spake thusly:
> Martin Vermeer wrote:
>
> > On Wed, Sep 17, 2003 at 10:52:48AM +0200, Lars Gullik Bjønnes spake
> > thusly:
> >
> >> what happens if you function call replace the default args with
> >> N_(...)
> >
> > ?
>
> N_(...) is j
Martin Vermeer wrote:
> On Wed, Sep 17, 2003 at 10:52:48AM +0200, Lars Gullik Bjønnes spake
> thusly:
>
>> what happens if you function call replace the default args with
>> N_(...)
>
> ?
N_(...) is just an empty macro (does nothing --- see src/gettext.h)
that enables the po files to document
On Wed, Sep 17, 2003 at 10:52:48AM +0200, Lars Gullik Bjønnes spake thusly:
> what happens if you function call replace the default args with
> N_(...)
?
> and use _(...) where the vars are used?
I did that... the new strings appear in the output.
> Or remove the _(..) from the default args
Martin Vermeer <[EMAIL PROTECTED]> writes:
| On Wed, Sep 17, 2003 at 10:21:54AM +0200, Lars Gullik Bjønnes spake thusly:
>>
>> Martin Vermeer <[EMAIL PROTECTED]> writes:
>>
>> >> Do we have any static objects? (we shouldn't) Global objects?
>> >
>> | Yes! in gettext.C:
>> >
>> | 24 Messages
Martin Vermeer <[EMAIL PROTECTED]> writes:
| On Wed, Sep 17, 2003 at 10:21:54AM +0200, Lars Gullik Bjønnes spake thusly:
>>
>> Martin Vermeer <[EMAIL PROTECTED]> writes:
>>
>> >> Do we have any static objects? (we shouldn't) Global objects?
>> >
>> | Yes! in gettext.C:
>> >
>> | 24 Messages
On Wed, Sep 17, 2003 at 10:21:54AM +0200, Lars Gullik Bjønnes spake thusly:
>
> Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> >> Do we have any static objects? (we shouldn't) Global objects?
> >
> | Yes! in gettext.C:
> >
> | 24 Messages & getLyXMessages()
> | 25 {
> | 26 stat
Martin Vermeer <[EMAIL PROTECTED]> writes:
>> Do we have any static objects? (we shouldn't) Global objects?
>
| Yes! in gettext.C:
>
| 24 Messages & getLyXMessages()
| 25 {
| 26 static Messages lyx_messages;
| 27
| 28 return lyx_messages;
| 29 }
| 30
|
On Wed, Sep 17, 2003 at 09:36:28AM +0200, Lars Gullik Bjønnes spake thusly:
>
> Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> | On Tue, Sep 16, 2003 at 09:49:52PM +, Angus Leeming spake thusly:
> |
> >> Martin Vermeer wrote:
> >> > H... is it possible that lang_ is being accessed after
Martin Vermeer <[EMAIL PROTECTED]> writes:
| On Tue, Sep 16, 2003 at 09:49:52PM +, Angus Leeming spake thusly:
|
>> Martin Vermeer wrote:
>> > H... is it possible that lang_ is being accessed after the
>> > containing class Messages::Pimpl has been destroyed?
>>
>> If so, I guess that t
On Tue, Sep 16, 2003 at 09:49:52PM +, Angus Leeming spake thusly:
> Martin Vermeer wrote:
> > H... is it possible that lang_ is being accessed after the
> > containing class Messages::Pimpl has been destroyed?
>
> If so, I guess that this is the kludge. Thereafter we'd have to
> ascerta
Martin Vermeer wrote:
> H... is it possible that lang_ is being accessed after the
> containing class Messages::Pimpl has been destroyed?
If so, I guess that this is the kludge. Thereafter we'd have to
ascertain _why_?
string const Messages::get(string const & msg) const
{
return pim
On Mon, Sep 15, 2003 at 09:56:22PM +, Angus Leeming spake thusly:
...
> What does valgrind say if you run lyx through that?
==10981==Address 0x421B6530 is 0 bytes inside a block of size 4 free'd
==10981==at 0x40028DF2: __builtin_delete (in
/home/mv/valgrind/lib/valgrind/vgskin_memc
On Mon, Sep 15, 2003 at 09:56:22PM +, Angus Leeming spake thusly:
...
> Ok, it looks to me like that 'lang_' member variable has been corrupted.
> Do you have LANG and LC_ALL environment variables set? Here I have
> $ echo "LANG=\"$LANG\" LC_ALL=\"$LC_ALL\""
> LANG="en_US" LC_ALL=""
>
> What
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
Could you perhaps compile src/messages.C with debug info.
$ touch src/messages.C
$ cd ${BUILDDIR}
$ make CXXFLAGS="-g -W -Wall"
>>>
>> | Did that. The interesting part of the backtrace:
>>>
>> Stuff like thi
On Mon, Sep 15, 2003 at 09:56:22PM +, Angus Leeming spake thusly:
>
> Martin Vermeer wrote:
> >> Is it not sufficient to compile the file that is causing the SIGSEGV in
> >> this way? If so, then the prescription above should be enough, no?
> >>
> > I did that too (but only recompiling messag
Martin Vermeer wrote:
>> Is it not sufficient to compile the file that is causing the SIGSEGV in
>> this way? If so, then the prescription above should be enough, no?
>>
> I did that too (but only recompiling messages.C). Backtrace (partly):
>
> ---
> #4 0x8123726 in error_handler ()
> #5 0x402
On Mon, Sep 15, 2003 at 05:33:41PM +, Angus Leeming spake thusly:
> Lars Gullik Bjønnes wrote:
> >>> Could you perhaps compile src/messages.C with debug info.
> >>> $ touch src/messages.C
> >>> $ cd ${BUILDDIR}
> >>> $ make CXXFLAGS="-g -W -Wall"
> >>
> > | Did that. The interesting part of t
Lars Gullik Bjønnes wrote:
>>> Could you perhaps compile src/messages.C with debug info.
>>> $ touch src/messages.C
>>> $ cd ${BUILDDIR}
>>> $ make CXXFLAGS="-g -W -Wall"
>>
> | Did that. The interesting part of the backtrace:
>>
> Stuff like this can be hard to debug, and if you are using the
> de
Martin Vermeer <[EMAIL PROTECTED]> writes:
| On Mon, Sep 15, 2003 at 05:13:05PM +, Angus Leeming spake thusly:
|
>> Martin Vermeer wrote:
>
| ...
|
>> I have followed your prescription exactly. Nada.
>
| ...
|
>> Could you perhaps compile src/messages.C with debug info.
>> $ touch src/me
On Mon, Sep 15, 2003 at 05:13:05PM +, Angus Leeming spake thusly:
> Martin Vermeer wrote:
...
> I have followed your prescription exactly. Nada.
...
> Could you perhaps compile src/messages.C with debug info.
> $ touch src/messages.C
> $ cd ${BUILDDIR}
> $ make CXXFLAGS="-g -W -Wall"
D
Martin Vermeer wrote:
> On Mon, Sep 15, 2003 at 04:28:45PM +, Angus Leeming spake thusly:
>>
>> Martin Vermeer wrote:
>>
>> > Create an inset, and an inset inside it, and copy/paste the second one
>> > to somewhere else inside the first. Then try to exit. LyX will core
>> > dump. (Not if eit
On Mon, Sep 15, 2003 at 04:28:45PM +, Angus Leeming spake thusly:
> Martin Vermeer wrote:
>
> > Create an inset, and an inset inside it, and copy/paste the second one
> > to somewhere else inside the first. Then try to exit. LyX will core
> > dump. (Not if either source or target inset are out
On Mon, Sep 15, 2003 at 04:28:45PM +, Angus Leeming spake thusly:
>
> Martin Vermeer wrote:
>
> > Create an inset, and an inset inside it, and copy/paste the second one
> > to somewhere else inside the first. Then try to exit. LyX will core
> > dump. (Not if either source or target inset are
Martin Vermeer wrote:
> Create an inset, and an inset inside it, and copy/paste the second one
> to somewhere else inside the first. Then try to exit. LyX will core
> dump. (Not if either source or target inset are outside the first
> inset.)
All seems fine here. Could you be more precise. What i
Create an inset, and an inset inside it, and copy/paste the second one
to somewhere else inside the first. Then try to exit. LyX will core
dump. (Not if either source or target inset are outside the first
inset.)
Reverting the lockInsetInInset patch didn't make a difference.
I don't think this is
46 matches
Mail list logo
