Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Georg Baum wrote:
| > Abdelrazak Younes wrote:
| >
| >> OK. The fix is simple. As you know the Application instance is not
| >> created when the export command-line feature is requested. This patch
| >> fixes the crash an
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Georg Baum wrote:
| > Abdelrazak Younes wrote:
| >
| >> OK. The fix is simple. As you know the Application instance is not
| >> created when the export command-line feature is requested. This patch
| >> fixes the crash and goes in soon.
| > So it is
Georg Baum wrote:
Abdelrazak Younes wrote:
Georg Baum wrote:
Abdelrazak Younes wrote:
OK. The fix is simple. As you know the Application instance is not
created when the export command-line feature is requested. This patch
fixes the crash and goes in soon.
So it is not possible to use the s
Abdelrazak Younes wrote:
> Georg Baum wrote:
>> Abdelrazak Younes wrote:
>>
>>> OK. The fix is simple. As you know the Application instance is not
>>> created when the export command-line feature is requested. This patch
>>> fixes the crash and goes in soon.
>>
>> So it is not possible to use th
Georg Baum wrote:
Others already pointed out that putting everything into a single global
variable might not always be the best solution. In this case it looks to me
like the connection of server and Application is artificial.
Of course, in this case this has nothing to do with using putting
Georg Baum wrote:
Abdelrazak Younes wrote:
Georg Baum wrote:
Abdelrazak Younes wrote:
OK. The fix is simple. As you know the Application instance is not
created when the export command-line feature is requested. This patch
fixes the crash and goes in soon.
So it is not possible to use the s
Abdelrazak Younes wrote:
> Georg Baum wrote:
>> Abdelrazak Younes wrote:
>>
>>> OK. The fix is simple. As you know the Application instance is not
>>> created when the export command-line feature is requested. This patch
>>> fixes the crash and goes in soon.
>>
>> So it is not possible to use th
Georg Baum wrote:
Abdelrazak Younes wrote:
OK. The fix is simple. As you know the Application instance is not
created when the export command-line feature is requested. This patch
fixes the crash and goes in soon.
So it is not possible to use the server in commandline mode? I am not sure
whet
Georg Baum wrote:
Abdelrazak Younes wrote:
OK. The fix is simple. As you know the Application instance is not
created when the export command-line feature is requested. This patch
fixes the crash and goes in soon.
So it is not possible to use the server in commandline mode? I am not sure
whet
Abdelrazak Younes wrote:
> This is what I get at the console:
>
> Traceback (most recent call last):
>File "d:/devel/lyx/trunk/lib/lyx2lyx/lyx2lyx", line 91, in ?
> sys.exit(main(sys.argv))
>File "d:/devel/lyx/trunk/lib/lyx2lyx/lyx2lyx", line 84, in main
> file.convert()
>Fi
Abdelrazak Younes wrote:
> OK. The fix is simple. As you know the Application instance is not
> created when the export command-line feature is requested. This patch
> fixes the crash and goes in soon.
So it is not possible to use the server in commandline mode? I am not sure
whether this is good
Abdelrazak Younes wrote:
By the way, I think lyx2lyx has not been updated with the format change.
This is what I get at the console:
Traceback (most recent call last):
File "d:/devel/lyx/trunk/lib/lyx2lyx/lyx2lyx", line 91, in ?
sys.exit(main(sys.argv))
File "d:/devel/lyx/trunk/lib/ly
Georg Baum wrote:
Abdelrazak Younes wrote:
I just had a look at the code and I don't see anything wrong at first
glance. Do you have a recipe to reproduce that?
I got it with an assertion in the InsetCommandParams constructor when trying
to read an invalid file. Just add
BOOST_ASSERT(false)
Abdelrazak Younes wrote:
> I just had a look at the code and I don't see anything wrong at first
> glance. Do you have a recipe to reproduce that?
I got it with an assertion in the InsetCommandParams constructor when trying
to read an invalid file. Just add
BOOST_ASSERT(false)
to it, and try to
Georg Baum wrote:
Abdel,
if something goes wrong and LyX::emergencyCleanup is called, then the
global Application object is already destroyed:
#0 0xb7f56410 in ?? ()
#1 0xbf90cb7c in ?? ()
#2 0x0006 in ?? ()
#3 0xb7101fb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#4 0x08544f91 in
15 matches
Mail list logo
