Here is some gdb output:

-------------------8<-----------------------

[EMAIL PROTECTED] ~/python/smerp $ gdb scite
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under
certain conditions. Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details. This GDB was configured as "i686-pc-linux-gnu"...(no debugging
symbols found) Using host libthread_db library
"/lib/tls/libthread_db.so.1".

(gdb) run db_user.py
Starting program: /usr/bin/scite db_user.py
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1219307840 (LWP 12726)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1219307840 (LWP 12726)]
0xb7b9bce4 in gdk_x11_register_standard_event_type ()
   from /usr/lib/libgdk-x11-2.0.so.0
(gdb) The program is running.  Exit anyway? (y or n) y
[8]+  Speicherzugriffsfehler  scite db_user.py

redmagic peters # equery b /usr/lib/libgdk-x11-2.0.so.0
[ Searching for file(s) /usr/lib/libgdk-x11-2.0.so.0 in *... ]
x11-libs/gtk+-2.8.12 (/usr/lib/libgdk-x11-2.0.so.0 ->
libgdk-x11-2.0.so.0.800.12)

-------------------8<-----------------------
At this point I edited some python code and was releasing the [shift] +
[f] keys.
libgdk-x11-2.0.so.0 belongs to gtk+...

ervin


On Sat, 8 Apr 2006 10:16:31 +1000
"Neil Hodgson" <[EMAIL PROTECTED]> wrote:

>Ervin Peters:
>
>> I'm just editing some perl:
>
>   OK, the file appears to be OK with a UTF-8 encoding cookie and a
>single non-ASCII character "ä" in a comment. It works quite well for
>me and doesn't crash or produce warnings when modifying "first". This
>is on Fedora Core 4. One thing to try is removing the "ä" and see it
>it still crashes as that could narrow the problem down.
>
>> [EMAIL PROTECTED] /mnt/balu/pool2000/abgleich $ strace scite gdidb.pm
>> [...]
>> poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}], 2, 99) = 0
>> gettimeofday({1144231123, 957408}, NULL) = 0
>> ioctl(3, FIONREAD, [0])                 = 0
>> gettimeofday({1144231123, 957528}, NULL) = 0
>> poll([{fd=3, events=POLLIN, revents=POLLIN}, {fd=4, events=POLLIN}],
>> 2, 100) = 1ioctl(3, FIONREAD, [64])                = 0 read(3,
>> "\0032|A\265\271\227\4\25\1\0\0\4\0\200\2\0\0\0\0\227\1"..., 64) =
>> 64 gettimeofday({1144231124, 10604}, NULL) = 0 gettimeofday
>> ({1144231124, 10913}, NULL) = 0 poll([{fd=3, events=POLLIN}, {fd=4,
>> events=POLLIN}], 2, 0) = 0 --- SIGSEGV (Segmentation fault) @ 0 (0)
>> --- +++ killed by SIGSEGV +++
>
>   OK, up to the SIGSEGV. You may be able to find more by running
>
>gdb SciTE
>
>   wait for a prompt
>
>run --synchronous gdidb.pm
>
>   use until dead
>
>bt
>
>   This will produce a stack trace of the failure location. The
>--synchronous may not be needed and it makes the program run very
>slowly but it means that the stack trace can accurately locate the
>error if it involves communication with the X server.
>
>   Neil
>
>_______________________________________________
>Scite-interest mailing list
>[email protected]
>http://mailman.lyra.org/mailman/listinfo/scite-interest


--
Ervin Peters
D-99425 Taubach

_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest

Reply via email to