|
| Re: Crash with empty Labels on Linux [message #198657 is a reply to message #198469] |
Wed, 12 October 2005 15:53   |
Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
This sounds like a nasty bug. Can you please provide us with a snippet that
reproduces it?
"Max" <mbrigl@gmx.net> wrote in message
news:pan.2005.10.12.07.00.57.225057@gmx.net...
> instantiating Labels (from draw2D) with no initial text the application
> crashes with following error (only on linux, on windows the application
> works fine):
>
> ------------------------------------------------------ The
> program 'SWT' received an X Window System error. This probably reflects a
> bug in the program. The error was 'BadAlloc (insufficient resources for
> operation)'.
> (Details: serial 4345 error_code 11 request_code 53 minor_code 0) (Note
> to programmers: normally, X errors are reported asynchronously;
> that is, you will receive the error a while after causing it. To debug
> your program, run it with the --sync command line option to change this
> behavior. You can then get a meaningful backtrace from your debugger if
> you break on the gdk_x_error() function.)
> ----------------------------------------------------- Trying to find a
> workaround I set a MarginBorder(1) on the Label the problem seems to be
> resolved.
>
> regards
|
|
|
| Re: Crash with empty Labels on Linux [message #198723 is a reply to message #198657] |
Wed, 12 October 2005 17:03 |
| Eclipse User |
|
|
|
Originally posted by: bbiggs.ca.ibm.com
A snippet would be very helpful. X is asynchronous, but in SWT there is
a way to put it in synchronous mode so you can get a stack trace of
where the failure occurs. When creating the display:
Device.DEBUG = true;
DeviceData data = new DeviceData();
data.debug = true;
Display display = new Display (data);
The X request which is failing here is an XCreatePixmap, so this might
have to do with an icon somewhere failing...
Randy Hudson wrote:
> This sounds like a nasty bug. Can you please provide us with a snippet that
> reproduces it?
>
> "Max" <mbrigl@gmx.net> wrote in message
> news:pan.2005.10.12.07.00.57.225057@gmx.net...
>
>>instantiating Labels (from draw2D) with no initial text the application
>>crashes with following error (only on linux, on windows the application
>>works fine):
>>
>>------------------------------------------------------ The
>>program 'SWT' received an X Window System error. This probably reflects a
>>bug in the program. The error was 'BadAlloc (insufficient resources for
>>operation)'.
>> (Details: serial 4345 error_code 11 request_code 53 minor_code 0) (Note
>> to programmers: normally, X errors are reported asynchronously;
>> that is, you will receive the error a while after causing it. To debug
>> your program, run it with the --sync command line option to change this
>> behavior. You can then get a meaningful backtrace from your debugger if
>> you break on the gdk_x_error() function.)
>>----------------------------------------------------- Trying to find a
>>workaround I set a MarginBorder(1) on the Label the problem seems to be
>>resolved.
>>
>>regards
>
>
>
|
|
|
| Re: Crash with empty Labels on Linux [message #198931 is a reply to message #198723] |
Thu, 13 October 2005 13:48 |
 Markus Brigl
Messages: 10
Registered: July 2009 |
Junior Member |
|
|
Hi,
I will provide a snippet as soon as possible. Unfortunately I can
reproduce the problem only on our application, but not in a simple
standalone.
On Wed, 12 Oct 2005 13:03:44 -0400, Billy Biggs wrote:
> A snippet would be very helpful. X is asynchronous, but in SWT there is
> a way to put it in synchronous mode so you can get a stack trace of
> where the failure occurs. When creating the display:
>
> Device.DEBUG = true;
> DeviceData data = new DeviceData();
> data.debug = true;
> Display display = new Display (data);
>
> The X request which is failing here is an XCreatePixmap, so this might
> have to do with an icon somewhere failing...
>
> Randy Hudson wrote:
>> This sounds like a nasty bug. Can you please provide us with a snippet that
>> reproduces it?
>>
>> "Max" <mbrigl@gmx.net> wrote in message
>> news:pan.2005.10.12.07.00.57.225057@gmx.net...
>>
>>>instantiating Labels (from draw2D) with no initial text the application
>>>crashes with following error (only on linux, on windows the application
>>>works fine):
>>>
>>>------------------------------------------------------ The
>>>program 'SWT' received an X Window System error. This probably reflects a
>>>bug in the program. The error was 'BadAlloc (insufficient resources for
>>>operation)'.
>>> (Details: serial 4345 error_code 11 request_code 53 minor_code 0) (Note
>>> to programmers: normally, X errors are reported asynchronously;
>>> that is, you will receive the error a while after causing it. To debug
>>> your program, run it with the --sync command line option to change this
>>> behavior. You can then get a meaningful backtrace from your debugger if
>>> you break on the gdk_x_error() function.)
>>>----------------------------------------------------- Trying to find a
>>>workaround I set a MarginBorder(1) on the Label the problem seems to be
>>>resolved.
>>>
>>>regards
>>
>>
>>
|
|
|
| Re: Crash with empty Labels on Linux [message #198939 is a reply to message #198723] |
Thu, 13 October 2005 14:06 |
| Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
"Billy Biggs" <bbiggs@ca.ibm.com> wrote in message
news:dijflh$a39$1@news.eclipse.org...
>A snippet would be very helpful. X is asynchronous, but in SWT there is
> a way to put it in synchronous mode so you can get a stack trace of
> where the failure occurs. When creating the display:
>
> Device.DEBUG = true;
> DeviceData data = new DeviceData();
> data.debug = true;
> Display display = new Display (data);
>
Billy, can this be done by using the PDE launcher's Tracing Tab?
|
|
|
| Re: Crash with empty Labels on Linux [message #199138 is a reply to message #198939] |
Thu, 13 October 2005 20:24 |
| Eclipse User |
|
|
|
Originally posted by: bbiggs.ca.ibm.com
Randy Hudson wrote:
> "Billy Biggs" <bbiggs@ca.ibm.com> wrote in message
> news:dijflh$a39$1@news.eclipse.org...
>
>>A snippet would be very helpful. X is asynchronous, but in SWT there is
>>a way to put it in synchronous mode so you can get a stack trace of
>>where the failure occurs. When creating the display:
>>
>> Device.DEBUG = true;
>> DeviceData data = new DeviceData();
>> data.debug = true;
>> Display display = new Display (data);
>
> Billy, can this be done by using the PDE launcher's Tracing Tab?
Good call. If you enable tracing for org.eclipse.ui, one of
the options is "debug/swtdebug". This _should_ enable both Device.DEBUG
and data.debug, but it may only do the latter which would be less useful
in this case.
Try swtdebug, and if you don't get a stack trace, file a bug against
Platform > UI asking for more tracing options :)
-Billy
|
|
|
Powered by
FUDForum. Page generated in 0.06574 seconds
] 
Search
Help
Register
Login
Home
