f



Xemacs crashes: Fatal error: assertion failed, file xlwtabs.c, line 1997, *reply_width > 0 && *reply_height > 0 Fatal error (6)

Using XEmacs 21.4.15 together with gnus 5.10.6 XEmacs crashes with a core
file. when I start it in a teminal I get this error:
 Fatal error: assertion failed, file xlwtabs.c, line 1997, *reply_width >
 0 && *reply_height > 0
Fatal error (6).

The absolut strange thing is, it does not happen in all news-groups.
The other point, the crash does not produce a "core" file. Accourding to
the output in the terminal: 

No GDB on your system?  You may have DBX, or XDB, or SDB.  (Ask your
system administrator if you need help.) If no core file was produced,
enable them (often with `ulimit -c unlimited' in case of future recurrance
of the crash. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

How does one who does not know full command achieve this? 

thanks :-) 

Dragomir Kollaric: 
who admits he stole his signature from someone else :-) 
-- 
Strange it works but we don't know why: 
it's Windows it does not have bugs only features;
the _most_ often _heard_ lie of the 20th. century, 
will it  _continue_ in the third  Millennium?


0
dragomir
4/28/2004 1:07:21 PM
comp.emacs.xemacs 2750 articles. 0 followers. Post Follow

2 Replies
1474 Views

Similar Articles

[PageSpeed] 8

dragomir kollaric wrote:
> Using XEmacs 21.4.15 together with gnus 5.10.6 XEmacs crashes with a core
> file. when I start it in a teminal I get this error:
>  Fatal error: assertion failed, file xlwtabs.c, line 1997, *reply_width >
>  0 && *reply_height > 0
> Fatal error (6).
> 
> The absolut strange thing is, it does not happen in all news-groups.
> The other point, the crash does not produce a "core" file. Accourding to
> the output in the terminal: 
> 
> No GDB on your system?  You may have DBX, or XDB, or SDB.  (Ask your
> system administrator if you need help.) If no core file was produced,
> enable them (often with `ulimit -c unlimited' in case of future recurrance
> of the crash. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
A 'core' file is the state of the program when it crashed; It is
often disabled by default as it's not of any use unless you
wish to debug why the program crashed, and they can be pretty big.

The shell (command prompt if you come from a MS-Windows world)
controls whever a program it started is allowed to produce a core file.
This means that the syntax is also determined by the shell.

For Debian GNU Linux, your default shell is normally bash.
Assuming you started XEmacs from a shell, if you enter
ulimit -c unlimited
into the shell before you start XEmacs, then a core file
will be generated.

You can then examine the core file with gdb by entering

gdb xemacs core

(You may need the full path to XEmacs, and the core file might be
called 'core.xxxx' where xxxx is a number).

When GDB starts, enter
bt
p *reply_width
p *reply_height
quit

This will give some information about what XEmacs did wrong.


GDB mighn't be installed by default on Debian. If it isn't
then running, as root,
apt-get install gdb
should install it.



Core files may not be generated if:
    The 'ulimit -c' value is too low.
    You logged in as root.
    The current directory isn't writeable.
    What (signal) caused the crash isn't set
	to creat cores.
         (Abort is set to create core files,
          see  'man 7 signal' for more information)

See also 'man bash'  about the syntax about 'ulimit'



> How does one who does not know full command achieve this? 
> 
> thanks :-) 
> 
> Dragomir Kollaric: 
> who admits he stole his signature from someone else :-) 

0
Colin
4/28/2004 5:18:01 PM
Thanks Colin for your answer :-) 

On Wed, 28 Apr 2004 18:18:01 +0100, Colin S. Miller wrote:

> dragomir kollaric wrote:
>> Using XEmacs 21.4.15 together with gnus 5.10.6 XEmacs crashes with a core
>> file. when I start it in a teminal I get this error:
>>  Fatal error: assertion failed, file xlwtabs.c, line 1997, *reply_width >
>>  0 && *reply_height > 0
>> Fatal error (6).
>> 
>> The absolut strange thing is, it does not happen in all news-groups.
>> The other point, the crash does not produce a "core" file. Accourding to
>> the output in the terminal: 
>> 
>> No GDB on your system?  You may have DBX, or XDB, or SDB.  (Ask your
>> system administrator if you need help.) If no core file was produced,
>> enable them (often with `ulimit -c unlimited' in case of future recurrance
>> of the crash. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> 
> A 'core' file is the state of the program when it crashed; It is
> often disabled by default as it's not of any use unless you
> wish to debug why the program crashed, and they can be pretty big.
> 
> The shell (command prompt if you come from a MS-Windows world)
> controls whever a program it started is allowed to produce a core file.
> This means that the syntax is also determined by the shell.
> 
> For Debian GNU Linux, your default shell is normally bash.
> Assuming you started XEmacs from a shell, if you enter
> ulimit -c unlimited
> into the shell before you start XEmacs, then a core file
> will be generated.
> 
> You can then examine the core file with gdb by entering
> 
> gdb xemacs core
> 
> (You may need the full path to XEmacs, and the core file might be
> called 'core.xxxx' where xxxx is a number).
> 
> When GDB starts, enter
> bt
> p *reply_width
> p *reply_height
> quit
> 
> This will give some information about what XEmacs did wrong.
> 
> 
> GDB mighn't be installed by default on Debian. If it isn't
> then running, as root,
> apt-get install gdb
> should install it.
> 
> 
> 
> Core files may not be generated if:
>     The 'ulimit -c' value is too low.
>     You logged in as root.
>     The current directory isn't writeable.
>     What (signal) caused the crash isn't set
> 	to creat cores.
>          (Abort is set to create core files,
>           see  'man 7 signal' for more information)
> 
> See also 'man bash'  about the syntax about 'ulimit'
> 
> 
> 
>> How does one who does not know full command achieve this? 
>> 
>> thanks :-) 
>> 
>> Dragomir Kollaric: 
>> who admits he stole his signature from someone else :-)
Dragomir Kollaric: 
who admits he stole his signature from someone else :-) 
--
Strange it works but we don't know why: 
it's Windows it does not have bugs only features;
the _most_ often _heard_ lie of the 20th. century, 
will it  _continue_ in the third  Millennium?


0
dragomir
4/30/2004 9:47:20 AM
Reply:

Similar Artilces:

assert( x > 0.0 && 1 && x == 0.0 ) holding
I'm having problems with inconsistent floating point behavior resulting in e.g. assert( x > 0.0 && putchar('\n') && x == 0.0 ); holding. (Actually, my problem is the dual one where I get failed assertions for assertions that at first thought ought to hold, but that's not important.) At the end is a full program containing the above seemingly inconsistent assertion. On my x86 using gcc the assertion doesn't fail when x is of type double. AFAIK, what is happening is that at first x temporary resides in a 80 bit register with a higher precision t...

Saving vi from 8.2 >> 8.0 >> 7.1 and encounter many warnings
I saved a Vi from 8.2 >> 8.0 >> 7.1 and encountered many warnings. I can open the vi in 8.0. When it is opened in LV 7.1, there comes out error code 24. LV 7.1 fails to open the vi diagram. The warning message was attached here.     warnings.txt: http://forums.ni.com/attachments/ni/170/232354/1/warnings.txt ...

LabVIEW crashed when openning XControl Facade, and Init VI
XControl_Fatal error.PNG: http://forums.ni.com/attachments/ni/170/261642/1/XControl_Fatal error.PNG XControl_Fatal error1.PNG: http://forums.ni.com/attachments/ni/170/261642/2/XControl_Fatal error1.PNG ...

* * * Please Read And/Or Print This! * * * Press [Ctrl][P] Keys On Your Keyboard To Print >> June 1, 2004 8:23:43 pm >> http://115639.aceboard.net/forum2.php?rub=158&cat=61&login=115639&page=0#
* * * Please Read And/Or Print This! * * * Press [Ctrl][P] Keys On Your Keyboard To Print >> June 1, 2004 8:23:46 pm >> http://115639.aceboard.net/forum2.php?rub=158&cat=61&login=115639&page=0#id96 << * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Hi eprint10108, Hiding like a rat, You asked me if I was saved ? : http://115639.ace...

Why do I receive a &quot;Fatal internal error: &quot;fpsane.cpp&quot; line 399&quot; when saving?
Why do I receive a&nbsp; "Fatal internal error: "fpsane.cpp" line 399" when saving my VI? &nbsp; Thank you. Gustavo Hi Chris, But I could not solve the error that way. Actually, Labview is crashing with this error at any time when I am writing my VI. It simply crashes even if the VI is not running. I think the problem is not in my VI, because&nbsp;it runs normally in another machine, but must be with the Labview installation. I have reinstalled Labview three time already and the error continues. Any other ideas? Thanks, Gustavo hum... not yet. &nbsp; I rei...

Assertion `(&(&_m->os)->n)->initialized == K5_MUTEX_DEBUG_INITIALIZED' failed
Hello folks, I think, I discovered a bug or a regression, but I'm not sure whether it is related to krb5 or to uw-imap. The problem came up when upgrading from krb5 1.4.x to 1.5: ipop3d from uw-imap refuses any POP3 connection with the error message: g_initialize.c:97: gss_release_oid: Assertion `(&(&_m->os)->n)->initialized == K5_MUTEX_DEBUG_INITIALIZED' failed. Spoken with other words, uw-imap using krb5 1.5: > telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. ipop3d: g_initialize.c:97: gss_release_oid: Assertion...

How do I recover from>> pg_xlog/0000000000000000 (log file 0, segment 0) failed: No such file or directory
Hello, Is there a way to recover from the following error? I have (had) an existing database and wish not to lose the data tables. Thanks for any help, Pete [postgres@web2 /]$ pg_ctl start postmaster successfully started [postgres@web2 /]$ LOG: database system shutdown was interrupted at 2004-10-18 11:41:55 PDT LOG: open of /web2-disk1/grip/database/pg_xlog/0000000000000000 (log file 0, segment 0) failed: No such file or directory LOG: invalid primary checkpoint record LOG: open of /web2-disk1/grip/database/pg_xlog/0000000000000000 (log file 0, segment 0) failed:...

Error 7 occurred at Copy in ABAPI Dist New VI Library.vi-&gt;ABAPI Dist Chk for Destinations.vi-&gt;ABAPI Copy Files and Apply...
When I try to build executables in LabView 8.01 I get&nbsp;message: Error 7 occurred at Copy in ABAPI Dist New VI Library.vi-&gt;ABAPI Dist Chk for Destinations.vi-&gt;ABAPI Copy Files and Apply Settings.vi-&gt;EBEP_Invoke_Build_Engine.vi-&gt;EBUIP_Build_Invoke.vi-&gt;EBUIP_Build_Invoke.vi.ProxyCaller Do you get this message when building any executable or on a particular VI ?&nbsp; You can force LabVIEW to recompile the entire VI hierarchy in your project with CTRL+SHIFT+Run Button. Tunde. It'is OK. I solve my problem. I have some old vi's included from L...

MAX &gt;&gt; Tools &gt;&gt; RT Disk Utilities is disabled
Hi, &nbsp; I've got a problem creating a boot disk for my desktop pc. The whole MAX menu "Tools" &gt;&gt; "RT Disk Utilities" is disabled and I can't create my boot disk. Can u help me? &nbsp; Thanks, &nbsp; Jannes ...

Labview &quot;Fatal Internal Error &quot;memory.cpp&quot; line 1038
Hi, &nbsp; This is an example file provided by NI and can be found in Labview 8.2\examples\instr\niHSDIO: Dynamic Generation.lib. Inside this library, there is a file called "Dynamic Generation.vi". If I copied "Dynamic Generation.vi" to other place, the labview will crash. Error message: &nbsp; "Fatal Internal Error. "memory.cpp". Line 1038. Labview version 7.1.1. You will lose any unused work, please contact NI, etc, etc" &nbsp; In the mean time, the Windows freeze. Mouse right click no response. No status bar at the bottom of the screen. T...

Why do I have this message when declaring variableof type mwArray in my Borland C++ (6.0) application using Matlab dll:[Linker Fatal Error] Fatal: Type index 1275002112 is bad in module F:\Pro..
I want to use a dll compiled from Matlab 7.0, in my application coded with Borland C++ (6.0). I generate the xxxxxx.dll, and compiled de xxxxxxx.lib. In my cpp file I want to declare a mwArray variable and I have this message error: [Linker Fatal Error] Fatal: Type index 1275002112 is bad in module F:\Projets\ADPCI\Technique\Software\TestFEd\TestLibDeuxFois2-Fed\fnTes tLibDeuxFois.cpp Is there something things wrong with the file: mclcppclass.h ?? Appreciate your help. ...

sshd: ../../include/k5-thread.h:704: k5_mutex_finish_init_1: Assertion `(&(&m->os)->n)->initialized != K5_MUTEX_DEBUG_INITIALIZED' failed.
Has anyone seen this error before: sshd: ../../include/k5-thread.h:704: k5_mutex_finish_init_1: Assertion `(&(&m->os)->n)->initialized != K5_MUTEX_DEBUG_INITIALIZED' failed. We've encountered this error on RHEL 5 using MIT Kerberos and Openssh 4.7p1. Thanks, On Jan 22, 2008, at 15:40, psullivanva@gmail.com wrote: > Has anyone seen this error before: > > sshd: ../../include/k5-thread.h:704: k5_mutex_finish_init_1: Assertion > `(&(&m->os)->n)->initialized != K5_MUTEX_DEBUG_INITIALIZED' failed. > > We've encountered this erro...

Please confirm bug in SHLOMIF > Error-0.17 > Error
Hello Everyone, I was hoping someone could confirm a bug for me. I believe I have found a bug in the Error module. The Synopsis section shows this example: throw Error::Simple -text => "Oops!" if $other_condition; However, this style of instantiating a Error::Simple object is broken. The constructor for Error::Simple does not convert the parameters array into a hash as expected: 265 sub new { 266 my $self = shift; 267 my $text = "" . shift; 268 my $value = shift; 269 my(@args) = (); I believe it should be: 265 sub new { ...

rdataset.c:652: REQUIRE(dbp != ((void *)0) && *dbp == ((void *)0)) failed
We have had a failure of one of our BIND installations this morning. The failure happened at 01:51:45 BST on a machine that was effectively idle at the time. The previous messages logged by 'named' were 30 seconds before the crash and were a zone transfer from a Microsoft 2003 DNS server of an AD integrated zone. I can provide config files if they are useful. The version of BIND is a stock build from Fedora 9 - bind-9.5.1-2.P2.fc9.i386. Is this a known problem, should we upgrade to get away from it, any advice? Regards, HOward. _______________________________...

Web resources about - Xemacs crashes: Fatal error: assertion failed, file xlwtabs.c, line 1997, *reply_width > 0 && *reply_height > 0 Fatal error (6) - comp.emacs.xemacs

Resources last updated: 2/1/2016 10:54:27 AM