#71334 - shadowofdarkness - Sat Feb 11, 2006 10:42 pm
I just tried the new version of the xcomms program and have a new seg fault problem
Under 1.21 I can run "xcomms_static SendSave_mb.gba" and everything works perfect with the send button seg faulting it but that is already well know
Under 1.22 the send button works perfect but when I start sending the program (either opening it with the button or on the command line) it seg faults. the gba does recieve a little data as the screen goes black.
#72011 - Honkey Kong - Thu Feb 16, 2006 12:10 am
Could you provide a little bit of information about the system you're running it on, like the Distribution, Kernel version, etc? I'm pretty sure that could be helpful in finding a way to reproduce the error, and narrowing it down to either a problem with your particular setup, or XComms itself.
#72049 - wintermute - Thu Feb 16, 2006 4:00 am
Would also help if you could determine what address is causing the segfault. Run the app through gdb & see what address it's trying to access.
It sounds like the GBA has booted at this point since the screen has gone black. This would indicate that the multi boot has completed successfully.
I don't actually understand why it would crash since no code in that area has changed. All I've really done is stop using a particular fltk widget library for the file selector.
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog
#72145 - shadowofdarkness - Thu Feb 16, 2006 5:55 pm
For my system I am running "Linux From Scratch" setup in sept 2004 with kernel 2.6.15.3
I will try running it in gdb but first I have to download and install + learn the basics of how to use it
#72157 - shadowofdarkness - Thu Feb 16, 2006 7:38 pm
I have tried gdb but since I don't program I don't understand it and just got the basics of running from the docs
First there is a little difference when running in gdb as it leave the gui open with some output whereas when running xcomms straight it closes
Well when run in gdb and it leaves the gui open it gets to the point of "Final Confirmation: Success" and the nothing
the output of gdb is
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"...Using host libthread_db library "/lib/libthread_db.so.1".
Setting up the environment for debugging gdb.
Function "internal_error" not defined.
Function "info_command" not defined.
.gdbinit:8: Error in sourced command file:
No breakpoint number 0.
(gdb) run
Starting program: /usr/bin/xcomms
[Thread debugging using libthread_db enabled]
[New Thread -1211572112 (LWP 12216)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1211572112 (LWP 12216)]
0x0804cbbc in _ReadSOState ()
#72179 - wintermute - Thu Feb 16, 2006 10:34 pm
#72228 - yuriks - Fri Feb 17, 2006 2:41 am
I have the same problem, Slackware 10.2, Kernel 2.6.15.
The multiboot completes and then segfaults (GBA runs fine)
Using xcomms (not _static)
Will try you new version and see if it fixes.
_________________
---yuriks---
#72253 - shadowofdarkness - Fri Feb 17, 2006 6:13 am
The new version still seg faults here is the new gdb output
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/libthread_db.so.1".
Setting up the environment for debugging gdb.
Function "internal_error" not defined.
Function "info_command" not defined.
.gdbinit:8: Error in sourced command file:
No breakpoint number 0.
(gdb) run
Starting program: /home/darkshadow/xcomms
(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 -1212104592 (LWP 12357)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1212104592 (LWP 12357)]
0x0804cbbc in ?? ()
#72264 - wintermute - Fri Feb 17, 2006 7:02 am
#72267 - shadowofdarkness - Fri Feb 17, 2006 7:37 am
I ran info registers in gdb after running the program and got this output
eax 0x1 1
ecx 0x4 4
edx 0x377 887
ebx 0x0 0
esp 0xbfc8a788 0xbfc8a788
ebp 0xbfc8a7c8 0xbfc8a7c8
esi 0x78b58c40 2025163840
edi 0x4415af1d 1142271773
eip 0x804cbbc 0x804cbbc <XMapRaised@plt+532>
eflags 0x210206 2163206
cs 0x73 115
ss 0x7b 123
ds 0x7b 123
es 0x7b 123
fs 0x0 0
gs 0x33 51
#72270 - wintermute - Fri Feb 17, 2006 8:08 am
#72272 - shadowofdarkness - Fri Feb 17, 2006 8:18 am
That worked perfect thanks.
#72274 - wintermute - Fri Feb 17, 2006 8:26 am