headers
willem | 1 Jan 04:33
Picon
Favicon

Dbugger error

Well I get an debugger error.

Lazarus # 0.9.24 beta i386-linux-gtk

steps to reproduce:

1 create new project.
2 choose console application.
3 create
4 save change to project
5 applicationname test
6 source editor add line : writeln('test');
7 run -> buildall
8 file -> save all
9 save project1 -> OK
10 overwrite? -> yes
11 run ->  "Nothing seems to happen "
12 run -> stop  --> "execution stopped "
13 run parameters  -> check  launching application
14 run ->   debugger : failed to load file  error message
15 press OK
16 lazarus run output window popup
17 press Enter
18 execution stopped -> press enter
19 debugger error : OOPS the debugger entered the error state.
20 GNU gdb 6.6-debian
    revision i486-linux-gnu

If I run a console application, the debugger seems to interfere.
but do not want  to  debug the console application, just run it.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Florian Klaempfl | 1 Jan 11:55
Favicon

Re: Making GTK Thread Safe

Giuliano Colla schrieb:
>> Isn't that where the dead lock occurs? Suppose Thr1 has just called
>> Synchronize and is waiting until the main thread has executed the
>> synchronized method, it won't terminate, because you have suppended
>> the main thread by waiting for Thr1 to terminate.
>>
> I'm afraid you're right.
> A really bullet proof way to terminate an application when even a single
> thread using synchronize is running is far from straightforward, and
> hard to generalize.
> For this reason, and many others, I consider the synchronize method just
> a hack.

Terminating threads is always not easy and hard to generalize.
Permalink | Reply | 3 comments |
headers
Sam Liddicott | 1 Jan 12:12

RE: Making GTK Thread Safe

Gmane came to mind, but it has the same problem, you can't use your nntp newsreader if port 119 is blocked.
Sam

-----Original Message-----
From: Micha Nelissen <micha <at> neli.hopto.org>
Sent: 31 December 2007 21:34
To: lazarus <at> miraclec.com
Subject: Re: [lazarus] Making GTK Thread Safe

Sam Liddicott wrote:
> I can smell an NNTP over http proxy.
> For syncronous commands and with HTTP keep-alive it should be nearly as eficient as regular NNTP

Simply use gmane?

Micha

_________________________________________________________________
     To unsubscribe: mail lazarus-request <at> miraclec.com with
                "unsubscribe" as the Subject
   archives at http://www.lazarus.freepascal.org/mailarchives
Permalink | Reply | 1 comment |
headers
Micha Nelissen | 1 Jan 12:27

Re: Making GTK Thread Safe

Sam Liddicott wrote:
> Gmane came to mind, but it has the same problem, you can't use your nntp newsreader if port 119 is blocked.

Gmane has a web interface also, e.g.:

http://news.gmane.org/gmane.comp.ide.lazarus.general

Micha
Permalink | Reply | 0 comments |
headers
Sam Liddicott | 1 Jan 12:44

RE: Making GTK Thread Safe

Yes.... But you can't use your newsreader, you have to use a web browser.

Sam

-----Original Message-----
From: Micha Nelissen <micha <at> neli.hopto.org>
Sent: 01 January 2008 11:27
To: lazarus <at> miraclec.com
Subject: Re: [lazarus] Making GTK Thread Safe

Sam Liddicott wrote:
> Gmane came to mind, but it has the same problem, you can't use your nntp newsreader if port 119 is blocked.

Gmane has a web interface also, e.g.:

http://news.gmane.org/gmane.comp.ide.lazarus.general

Micha

_________________________________________________________________
     To unsubscribe: mail lazarus-request <at> miraclec.com with
                "unsubscribe" as the Subject
   archives at http://www.lazarus.freepascal.org/mailarchives
Permalink | Reply | 2 comments |
headers
Micha Nelissen | 1 Jan 12:52

Re: Making GTK Thread Safe

Sam Liddicott wrote:
> Yes.... But you can't use your newsreader, you have to use a web browser.

So? You're also not allowed to use a web browser?

Btw, your email client is broken: it doesn't have the In-Reply-To and
References email headers. Please consider using another one.

Micha
Permalink | Reply | 1 comment |
headers
Paul Ishenin | 1 Jan 14:02
Picon

Re: Some nice bugs to start the new year...

Michael Van Canneyt wrote:
> - Latest SVN:
>   Adding a file in the image list editor crashes the fileopen dialog:
>
>   
[skip]

fixed in r13556

Best regards,
Paul Ishenin.
Permalink | Reply | 1 comment |
headers
Sam Liddicott | 1 Jan 14:13

Re: Making GTK Thread Safe

Micha Nelissen wrote:
> Sam Liddicott wrote:
>   
>> Yes.... But you can't use your newsreader, you have to use a web browser.
>>     
>
> So? You're also not allowed to use a web browser?
>   
I think the thread got lost... so to refresh where I came in:

On Thu, Dec 13, 2007 at 04:35:24PM +0300, Al Boldi wrote:
 > Graeme Geldenhuys wrote:
 > > On 13/12/2007, Martin Schreiber <fpmse <at> bluewin.ch> wrote:
 > > > > Is there web gateway for this?
 > > > >
 > > > No, use a news client, Mozilla Thunderbird for win32/Linux or
 > > > KNode for Linux for example. You will probably like the conversation
 > > > by NNTP, much more convenient than mailing lists or web forums IMHO.
 > >
 > > I can't agree more.  NNTP is a lot more convenient and preferred by
 > > me, that mailing list.
 >
 > The problem is that sometimes NNTP ports are blocked.

And I also prefer NNTP access.
So yes there may well be NNTP gmane access but I still smell a 
NNTP->HTTP gateway.
> Btw, your email client is broken: it doesn't have the In-Reply-To and
> References email headers. Please consider using another one.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Van Canneyt | 1 Jan 14:19
Favicon

Re: Some nice bugs to start the new year...


On Tue, 1 Jan 2008, Paul Ishenin wrote:

> Michael Van Canneyt wrote:
> > - Latest SVN:
> >   Adding a file in the image list editor crashes the fileopen dialog:
> >
> >   
> [skip]
> 
> fixed in r13556

Great, thank you.

I tested my posted patch for the imagelist problem, and that works fine, so I suppose
you can apply it as well. (bug 10527)

Great service, thanks a lot :-)

Michael.
Permalink | Reply | 0 comments |
headers
Giuliano Colla | 1 Jan 14:39
Picon
Gravatar

Re: Making GTK Thread Safe

Florian Klaempfl ha scritto:
> Giuliano Colla schrieb:
>   
>>> Isn't that where the dead lock occurs? Suppose Thr1 has just called
>>> Synchronize and is waiting until the main thread has executed the
>>> synchronized method, it won't terminate, because you have suppended
>>> the main thread by waiting for Thr1 to terminate.
>>>
>>>       
>> I'm afraid you're right.
>> A really bullet proof way to terminate an application when even a single
>> thread using synchronize is running is far from straightforward, and
>> hard to generalize.
>> For this reason, and many others, I consider the synchronize method just
>> a hack.
>>     
>
> Terminating threads is always not easy and hard to generalize.
>
>   
You're right, but the available tools can make it easier or harder.
I come from a long experience in real-time applications, with many 
concurrent interrelated tasks, and if the design isn't sound enough you 
end up with deadlocks at each corner.
What I don't like is a mechanism which may create deadlocks you're 
unaware of, because they're dependent on GUI implementation. With a 
simple test application I've found different behaviors on Kylix 1, Kylix 
3, different versions of Lazarus, and even in the same Lazarus version 
with different widgetsets.
(Continue reading)

Permalink | Reply | 2 comments |

Gmane