Il 06/01/2011 09:59, Vincent van Ravesteijn ha scritto:
Last,
Have you ever thought about a search history ?
Yes, sometimes, even though I'm not sure about the possible user
interface for that.
Perhaps two little arrows somewhere which, when pushed, navigate through the
last performed searc
On Thu, Jan 6, 2011 at 9:58 AM, Vincent van Ravesteijn wrote:
>> In principle this works out-of-the-box because the settings are
>> restored by Qt.
>
> What I forgot to say is:
>
Last,
Have you ever thought about a search history ?
Vincent
> In principle this works out-of-the-box because the settings are
> restored by Qt.
What I forgot to say is:
If you also want to remember the settings in the dialog, like
word-wrap, case-sensitivity and so on, you need to implement the
following two functions:
- void FindAndReplace::restoreSessi
On Wed, Jan 5, 2011 at 4:13 PM, Tommaso Cucinotta wrote:
> Il 05/01/2011 16:05, Vincent van Ravesteijn ha scritto:
>>
>> A side-effect also was that we don't remember the outliner visibility
>> status on exit, because all documents were closed on exit and also the
>> outliner then. I think you wan
On 01/05/2011 04:05 PM, Vincent van Ravesteijn wrote:
Op 5-1-2011 15:42, Tommaso Cucinotta schreef:
Il 05/01/2011 11:46, Jean-Marc Lasgouttes ha scritto:
Le 05/01/2011 00:21, Tommaso Cucinotta a écrit :
Ok, let's give up with the assumption that the Adv Search dialog can
only be open when a m
Il 05/01/2011 16:05, Vincent van Ravesteijn ha scritto:
A side-effect also was that we don't remember the outliner visibility
status on exit, because all documents were closed on exit and also the
outliner then. I think you want the find-replace widget also to be
remembered to the next sessio
Il 05/01/2011 00:21, Tommaso Cucinotta ha scritto:
If anyone likes it, I'll commit it.
Anyway, being a fix of a crash, I thought it is ok to commit anycase
(r37115).
(if later we come up with a means for closing the dialog when last
doc is closed, then this code is harmless).
T.
Op 5-1-2011 15:42, Tommaso Cucinotta schreef:
Il 05/01/2011 11:46, Jean-Marc Lasgouttes ha scritto:
Le 05/01/2011 00:21, Tommaso Cucinotta a écrit :
Ok, let's give up with the assumption that the Adv Search dialog can
only be open when a main document exists and is open.
I prefer to give up.
Il 05/01/2011 11:46, Jean-Marc Lasgouttes ha scritto:
Le 05/01/2011 00:21, Tommaso Cucinotta a écrit :
Ok, let's give up with the assumption that the Adv Search dialog can
only be open when a main document exists and is open. In fact the
following sequence is sufficient for violating it:
1) C-N
Le 05/01/2011 00:21, Tommaso Cucinotta a écrit :
Ok, let's give up with the assumption that the Adv Search dialog can
only be open when a main document exists and is open. In fact the
following sequence is sufficient for violating it:
1) C-N (new doc)
2) C-S-f (Adv Search panel)
3) C-w (close doc
Il 04/01/2011 18:24, John McCabe-Dansted ha scritto:
Keycodes:
'''\CF\Ae\[Right]L\Cq'''\[!Loop]
To reproduce:
1) Press Cntl-Shift-F to open the AdvFind dialog (KK: \CF)
2) Press F11 to go Fullscreen (KK: \Ae)
3) Press Cntl-Q to quit... (KK: \Cq)
I then get the following crash.
Arch: x86_64
Revi
Keycodes:
'''\CF\Ae\[Right]L\Cq'''\[!Loop]
To reproduce:
1) Press Cntl-Shift-F to open the AdvFind dialog (KK: \CF)
2) Press F11 to go Fullscreen (KK: \Ae)
3) Press Cntl-Q to quit... (KK: \Cq)
I then get the following crash.
Arch: x86_64
Revision: 37080
Regression in r37057
{{{
Program received
Bennett Helm wrote:
On Mac, anytime I make a change to LyX's preferences, I get a new "special"
menu appearing. Sometimes (and I'm not sure exactly under what conditions)
this leads to a crash while editing a document. But it *always* leads to a
crash if I try to quit. Here'
Could you please
Sorry for the incomplete message; let's try this again.
On Wed, Aug 27, 2008 at 2:54 PM, Bennett Helm <[EMAIL PROTECTED]> wrote:
> On Mac, anytime I make a change to LyX's preferences, I get a new "special"
> menu appearing. Sometimes (and I'm not sure exactly under what conditions)
> this leads
On Mac, anytime I make a change to LyX's preferences, I get a new "special"
menu appearing. Sometimes (and I'm not sure exactly under what conditions)
this leads to a crash while editing a document. But it *always* leads to a
crash if I try to quit. Here'
On Sat, Jul 12, 2008 at 6:33 AM, Uwe Stöhr <[EMAIL PROTECTED]> wrote:
> > Recently I've been getting occasional crashes on quit.
>
> I see this here too on Windows. Could you please report this at bugzilla so
> that this won't be forgotten?
>
> regards Uwe
>
Done:
http://bugzilla.lyx.org/show_bu
Pavel Sanda wrote:
> Bennett Helm wrote:
> > Program received signal EXC_BAD_ACCESS, Could not access memory.
> > Reason: KERN_INVALID_ADDRESS at address: 0x6163697c
> > std::_Rb_tree,
>
> iirc redblack trees were used in completion stuff, so maybe Stefan would
> have some idea.
no i was wrong, i
Bennett Helm wrote:
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x6163697c
> std::_Rb_tree,
iirc redblack trees were used in completion stuff, so maybe Stefan would
have some idea.
pavel
> std::less, std::allocator lyx::Messages>
> Recently I've been getting occasional crashes on quit.
I see this here too on Windows. Could you please report this at bugzilla so that this won't be
forgotten?
regards Uwe
Recently I've been getting occasional crashes on quit. Using gdb, I see
multiple messages like this when LyX is running:
lyx(98256,0xa019dfa0) malloc: *** mmap(size=1206730752) failed (error
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
After I qu
On Tue, Apr 29, 2008 at 09:24:41PM -0400, Bennett Helm wrote:
> On Tue, Apr 29, 2008 at 1:29 PM, Enrico Forestieri <[EMAIL PROTECTED]>
> wrote:
>
> > On Tue, Apr 29, 2008 at 10:56:52AM -0400, Bennett Helm wrote:
> > > Seeing Enrico's recent report of crash on
On Tue, Apr 29, 2008 at 1:29 PM, Enrico Forestieri <[EMAIL PROTECTED]>
wrote:
> On Tue, Apr 29, 2008 at 10:56:52AM -0400, Bennett Helm wrote:
> > Seeing Enrico's recent report of crash on quit on Windows, here's
> another
> > one on Mac. (Didn't look like th
On Tue, Apr 29, 2008 at 10:56:52AM -0400, Bennett Helm wrote:
> Seeing Enrico's recent report of crash on quit on Windows, here's another
> one on Mac. (Didn't look like the same problem to me, so I'm creating a new
> thread, but cc-ing Enrico just in case.) This has
I think it's the same, some double deletion of the pasteboards.
Stefan
Am 29.04.2008 um 16:56 schrieb Bennett Helm:
Seeing Enrico's recent report of crash on quit on Windows, here's
another
one on Mac. (Didn't look like the same problem to me, so I'm
creating
Seeing Enrico's recent report of crash on quit on Windows, here's another
one on Mac. (Didn't look like the same problem to me, so I'm creating a new
thread, but cc-ing Enrico just in case.) This has happened for a little
while now.
Program received signal EXC_BAD_ACCESS, Cou
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
I've found a solution without ::exit(0) which I've tested with
msvc/Qt4.2.1
and Linux/Qt4.1.3.
>>> I don't understand. Current svn doesn't need the ::exit(0) on Linux and
>>> Windows, so why is it a solution?
>>
>> It is a solution becau
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Exactly my point. With current svn, it is not necessary and everything
is destroyed in the correct order on Windows and I believe also Linux
without requiring a hard ::exit(0).
Does this mean needing ::exit(0) is a Qt bug?
I am not sure. The inter
Abdelrazak Younes wrote:
> Exactly my point. With current svn, it is not necessary and everything
> is destroyed in the correct order on Windows and I believe also Linux
> without requiring a hard ::exit(0).
Does this mean needing ::exit(0) is a Qt bug?
Peter
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Abdelrazak Younes wrote:
> I suggest that you test this carefully before applying. You don't want
to know how much time I spent to get it right on windows.
Do you see/have problems with the attached patch?
Here on windows it w
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>> > I suggest that you test this carefully before applying. You don't want
>>> to know how much time I spent to get it right on windows.
>>
>> Do you see/have problems with the attached patch?
>>
>> Here on windows it work
Peter Kümmel wrote:
Abdelrazak Younes wrote:
> I suggest that you test this carefully before applying. You don't want
to know how much time I spent to get it right on windows.
Do you see/have problems with the attached patch?
Here on windows it works fine. It also removes the
buggy Qt code.
Abdelrazak Younes wrote:
> I suggest that you test this carefully before applying. You don't want
> to know how much time I spent to get it right on windows.
Do you see/have problems with the attached patch?
Here on windows it works fine. It also removes the
buggy Qt code.
Bennett, could you pl
Peter Kümmel wrote:
Should I just check in this patch:
Index: src/frontends/qt4/GuiImplementation.C
===
--- src/frontends/qt4/GuiImplementation.C (revision 15972)
+++ src/frontends/qt4/GuiImplementation.C (working copy)
On Nov 19, 2006, at 12:59 PM, Peter Kümmel wrote:
Bennett Helm wrote:
This is really a endless story. here the next try.
Well, it turns out you're wrong again: it wasn't endless! This patch
(which I applied on top of the last one) fixes the problem.
Thanks!
Bennett
Great. Good that I was
Bennett Helm wrote:
>> This is really a endless story. here the next try.
>
> Well, it turns out you're wrong again: it wasn't endless! This patch
> (which I applied on top of the last one) fixes the problem.
>
> Thanks!
>
> Bennett
>
Great. Good that I was wrong. ;)
Does it also work with th
On Nov 19, 2006, at 12:37 PM, Peter Kümmel wrote:
Bennett Helm wrote:
The crash I got was on exit, not on startup. This time I deleted
.lyxpipe.in (from another instance of LyX I had running), and
tried 1.5
again. Again, a crash on exit, but a more informative backtrace:
(gdb) run
Starting
Bennett Helm wrote:
> On Nov 19, 2006, at 12:00 PM, Abdelrazak Younes wrote:
>
>> Bennett Helm wrote:
>>> On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
It looks like we rely on a Qt bug on Windows and on Linux.
Bennett could you please try the attached patch.
>>> Thanks, Peter. Howeve
On Nov 19, 2006, at 12:00 PM, Abdelrazak Younes wrote:
Bennett Helm wrote:
On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
It looks like we rely on a Qt bug on Windows and on Linux.
Bennett could you please try the attached patch.
Thanks, Peter. However, I still get a crash. Here's the only
Bennett Helm wrote:
On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
It looks like we rely on a Qt bug on Windows and on Linux.
Bennett could you please try the attached patch.
Thanks, Peter. However, I still get a crash. Here's the only backtrace I
get:
This is not a crash on exit but on
Bennett Helm wrote:
> On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
>
>> It looks like we rely on a Qt bug on Windows and on Linux.
>> Bennett could you please try the attached patch.
>
> Thanks, Peter. However, I still get a crash. Here's the only backtrace I
> get:
>
> Starting program: /Ap
On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
It looks like we rely on a Qt bug on Windows and on Linux.
Bennett could you please try the attached patch.
Thanks, Peter. However, I still get a crash. Here's the only
backtrace I get:
Starting program: /Applications/LyX-150.app/Contents/Ma
Angus Leeming wrote:
Georg Baum <[EMAIL PROTECTED]> writes:
Peter Kümmel wrote:
BTW, next time at a book shop, have a look at "Modern C++ Design" by
Andrei Alexandrescu.
I might do so.
Incidentally, whilst this book most definitely *is* a good investment, the
Singleton pattern was reimple
Peter Kümmel wrote:
Peter Kümmel wrote:
Peter Kümmel wrote:
Peter Kümmel wrote:
Bennett Helm wrote:
On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
Georg Baum wrote:
Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
Georg Baum wrote:
Peter Kümmel wrote:
My idea was to us
Bennett Helm wrote:
On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
This is what I did. Hopefully, all crash-on-exit problems on windows
and Mac should be solved now.
Unfortunately, not. Quitting LyX on Mac gives:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reaso
Peter Kümmel wrote:
> Peter Kümmel wrote:
>> Peter Kümmel wrote:
>>> Bennett Helm wrote:
On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
> Georg Baum wrote:
>> Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
>>> Georg Baum wrote:
Peter Kümmel wrote:
>
Peter Kümmel wrote:
> Peter Kümmel wrote:
>> Bennett Helm wrote:
>>> On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
>>>
Georg Baum wrote:
> Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
>> Georg Baum wrote:
>>> Peter Kümmel wrote:
>>>
My idea was to
Peter Kümmel wrote:
> Bennett Helm wrote:
>> On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
>>
>>> Georg Baum wrote:
Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
> Georg Baum wrote:
>> Peter Kümmel wrote:
>>
>>> My idea was to use some Loki code for singlet
Bennett Helm wrote:
> On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
>
>> Georg Baum wrote:
>>> Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
Georg Baum wrote:
> Peter Kümmel wrote:
>
>> My idea was to use some Loki code for singletons and global static
>>> dat
Angus Leeming wrote:
> Georg Baum <[EMAIL PROTECTED]> writes:
Peter Kümmel wrote:
>>> BTW, next time at a book shop, have a look at "Modern C++ Design" by
>>> Andrei Alexandrescu.
>
>> I might do so.
>
> Incidentally, whilst this book most definitely *is* a good investment, the
> Singleton
Georg Baum <[EMAIL PROTECTED]> writes:
> > > Peter Kümmel wrote:
> > BTW, next time at a book shop, have a look at "Modern C++ Design" by
> > Andrei Alexandrescu.
> I might do so.
Incidentally, whilst this book most definitely *is* a good investment, the
Singleton pattern was reimplemented as a
On Nov 18, 2006, at 12:50 PM, Abdelrazak Younes wrote:
Georg Baum wrote:
Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
Georg Baum wrote:
Peter Kümmel wrote:
My idea was to use some Loki code for singletons and global static
data.
I don't know Loki, so maybe I am missing somethi
Hello!
Maybe some help (i think i once posted it on the list): I don't have 1.5
yet so i can't test it there, but on two WinXP PCs all Versions of 1.4.3
crash also on exit if i turn on instant preview and close the lyx window
short time after opening a document (like e.g. the doc file
customi
Georg Baum wrote:
Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
Georg Baum wrote:
Peter Kümmel wrote:
My idea was to use some Loki code for singletons and global static
data.
I don't know Loki, so maybe I am missing something here, but I believe
that
we already have everything
Georg Baum wrote:
> Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
>> Georg Baum wrote:
>>> Peter Kümmel wrote:
>>>
My idea was to use some Loki code for singletons and global static
> data.
>>> I don't know Loki, so maybe I am missing something here, but I believe
> that
>>> we a
Am Freitag, 17. November 2006 21:06 schrieb Peter Kümmel:
> Georg Baum wrote:
> > Peter Kümmel wrote:
> >
> >> My idea was to use some Loki code for singletons and global static
data.
> >
> > I don't know Loki, so maybe I am missing something here, but I believe
that
> > we already have everyth
On Fri, Nov 17, 2006 at 04:57:14PM +0100, Peter Kümmel wrote:
> > Abdelrazak> This is something else... Do you have an idea Georg?
> >
> > Looks like prepareExit tries to use _() and the iconv stuff has
> > already been killed. Probably that the static IconvProcessor (in
> > utf8_to_ucs4) and the
Peter Kümmel wrote:
Abdelrazak Younes wrote:
avoid global static data!
Yes, maybe the remaining data could be centralized in one class which will
be create and deleted at one place. We should avoid that creation and
destruction is handled automatically by the compiler.
What do you think I
On Nov 17, 2006, at 11:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's
Georg Baum wrote:
> Peter Kümmel wrote:
>
>> My idea was to use some Loki code for singletons and global static data.
>
> I don't know Loki, so maybe I am missing something here, but I believe that
> we already have everything needed.
Yes, we have C++.
BTW, next time at a book shop, have a look
Peter Kümmel wrote:
> My idea was to use some Loki code for singletons and global static data.
I don't know Loki, so maybe I am missing something here, but I believe that
we already have everything needed.
>> avoid global static data!
>
> Yes, maybe the remaining data could be centralized in
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>>> Abdelrazak> Bennett Helm wrote:
> On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
>> Bennett Helm wrote:
>>> 1.5.0 alpha crashes
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new backtrace:
Please try again with last svn.
Ab
Peter Kümmel wrote:
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new backtrace:
Program received signal EXC_BAD_ACCE
Jean-Marc Lasgouttes wrote:
>> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
> Abdelrazak> Bennett Helm wrote:
>>> On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
> 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
> backtr
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new bac
Abdelrazak Younes wrote:
> Bennett Helm wrote:
>> On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
>>
>>> Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
>>>
>>> Could you try out this patch please?
>>
>> I still get a crash. Here's the
Jean-Marc Lasgouttes wrote:
> Looks like prepareExit tries to use _() and the iconv stuff has
> already been killed. Probably that the static IconvProcessor (in
> utf8_to_ucs4) and the LyX instance are not deleted in the right order.
That was exactly the result of my analysis, too.
Georg
On Nov 17, 2006, at 10:32 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out t
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Bennett Helm wrote:
>> On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
>>> Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
>>> Could you try out this patc
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new backtrace:
Program received signal EXC_BAD_ACCE
Bennett Helm wrote:
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new backtrace:
Program received signal EXC_BAD_ACCE
On Nov 17, 2006, at 5:59 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Could you try out this patch please?
I still get a crash. Here's the new backtrace:
Program received signal EXC_BAD_ACCESS, Could not access
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the backtrace:
Could you try out this patch please?
Thanks in advance,
Abdel.
Index: lyx_main.C
===
--- lyx_main.C (revision 15953)
+++ lyx_main.C
Peter Kümmel wrote:
> Sorry for not having fixed a bug which I've not introduced.
No need to be sorry. I am only a bit frustrated that probably the same bug
comes again and again.
Georg
Abdelrazak Younes wrote:
> Looks like I am responsible here but I don't regret anything. I will
> review this code and solve the problem before 1.5.0.
Fine.
Georg
Georg Baum wrote:
Am Donnerstag, 16. November 2006 12:41 schrieb Peter Kümmel:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Program received signal SIGABRT, Aborted.
0x9003d1dc in kill ()
(gdb) bt
#0 0x9003d1dc in kill ()
#1 0x9010f2af in ra
On Thursday 16 November 2006 11:40 pm, Peter Kümmel wrote:
> Sorry for not having fixed a bug which I've not introduced.
Don't worry I forgive you. ;-) (Only 7 minutes remains to be so magnanimous)
> Regards,
> Peter
--
José Abílio
Georg Baum wrote:
> Am Donnerstag, 16. November 2006 12:41 schrieb Peter Kümmel:
>> Bennett Helm wrote:
>>> 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
> backtrace:
>>> Program received signal SIGABRT, Aborted.
>>> 0x9003d1dc in kill ()
>>> (gdb) bt
>>> #0 0x9003d1dc in kill (
Am Donnerstag, 16. November 2006 12:41 schrieb Peter Kümmel:
> Bennett Helm wrote:
> > 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
> >
> > Program received signal SIGABRT, Aborted.
> > 0x9003d1dc in kill ()
> > (gdb) bt
> > #0 0x9003d1dc in kill ()
> > #1 0x9010f2
ompile!
Sorry, the patch was not complete, here a new one
and one with the missing part.
Thanks. The patch had the changes from Application.C twice, but it
compiles. However, I still get a crash on quit. Here's the new
backtrace:
Program received signal EXC_BAD_ACCESS, Could
Bennett Helm wrote:
> On Nov 16, 2006, at 6:41 AM, Peter Kümmel wrote:
>
>> Bennett Helm wrote:
>>> 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
>>> backtrace:
>>>
>>> Program received signal SIGABRT, Aborted.
>>> 0x9003d1dc in kill ()
>>> (gdb) bt
>>> #0 0x9003d1dc in kill ()
On Nov 16, 2006, at 6:41 AM, Peter Kümmel wrote:
Bennett Helm wrote:
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Program received signal SIGABRT, Aborted.
0x9003d1dc in kill ()
(gdb) bt
#0 0x9003d1dc in kill ()
#1 0x9010f2af in raise ()
#2 0x9010de02 in abor
Bennett Helm wrote:
> 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the backtrace:
>
> Program received signal SIGABRT, Aborted.
> 0x9003d1dc in kill ()
> (gdb) bt
> #0 0x9003d1dc in kill ()
> #1 0x9010f2af in raise ()
> #2 0x9010de02 in abort ()
> #3 0x90b4039c in __gnu_cxx::__v
1.5.0 alpha crashes every time on quit on Intel Mac. Here's the
backtrace:
Program received signal SIGABRT, Aborted.
0x9003d1dc in kill ()
(gdb) bt
#0 0x9003d1dc in kill ()
#1 0x9010f2af in raise ()
#2 0x9010de02 in abort ()
#3 0x90b4039c in __gnu_cxx::__verbose_terminate_handler ()
#4 0x9
LyX 1.5.0 crashes everytime on quit on Mac, and it causes OS X's
crashdump utility to go into what seems like an endless loop,
consuming all available processor time. Here's the backtrace:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at addr
This bug has gotten lost in the shuffle, so I thought I'd repost it.
(Others are now reporting the same problem when using LyX/Mac-140pre3.)
Bennett
On Oct 4, 2005, at 1:40 PM, Bennett Helm wrote:
I've occasionally been having lyx-140 crash on quitting. It doesn't
happen often enough that I
I've occasionally been having lyx-140 crash on quitting. It doesn't
happen often enough that I've seen a pattern, and I can't reliably
reproduce it.
Here's the backtrace:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00050a9b
0
89 matches
Mail list logo
