segmentation fault

Thread: segmentation fault

Search this list only Search all lists
segmentation fault
	2006-09-14 19:47:37

On 06-09-14, at 15:27, oliver oli wrote: > Jeremy Tregunna wrote: >> On 06-09-13, at 16:04, oliver oli wrote: >> >;>> hi, >>> >>> i compiled Io from the darcs repository. It segfaults imediatly. Any >>> idea what could be wrong? It's running on Debian (Etch) amd64. >>> >>> # make install >>> [...] >;>> # ldconfig >>>; # io >>> Segmentation fault >;> >> Please fire up io in gdb, and execute the 'run' command. When it >> crashes, get an output of the call stack ("bt full") and post it to >> the mailing list. This will help us help you more. >; > i'm not familiar with gdb, i hope this helps... > > (gdb) run io > Starting program: /usr/local/bin/io io > > Program received signal SIGSEGV, Segmentation fault. > 0x00002ae7ebbbaae7 in Coro_StartWithArg () from /usr/local/lib/ > libiovmall.so > (gdb) bt full > #0 0x00002ae7ebbbaae7 in Coro_StartWithArg () > from /usr/local/lib/libiovmall.so > No symbol table info available. > #1 0x00002ae7ebd49960 in swapcontext () from /lib/libc.so.6 > No symbol table info available. > #2 0x0000000000000000 in ?? () > No symbol table info available. > (gdb) That's not really helpful yet. Could you edit the toplevel Makefile.lib and find "OPTIMIZE". Change that to read: OPTIMIZE := -Os -g -fPIC Then make clean, and do a fresh build. Then try this again, showing us the results of the full call stack. Sorry, I should have made sure you had debugging flags on initially. -- Jeremy Tregunna jtregunnablurgle.ca __._,_.___ Messages in this topic (4) Reply (via web post) \| Start a new topic . __,_._,___
segmentation fault
	2006-09-14 19:58:59

Hi Jeremy and Oliver, On 9/15/06, Jeremy Tregunna <jtregunnablurgle.ca> wrote: > > That's not really helpful yet. Could you edit the toplevel > Makefile.lib and find "OPTIMIZE". Change that to read: >; > OPTIMIZE := -Os -g -fPIC Jeremy may have meant, OPTIMIZE := -g -fPIC Thanks, Jonathan. __._,_.___ Messages in this topic (5) Reply (via web post) \| Start a new topic . __,_._,___
segmentation fault
	2006-09-15 08:13:37

Jeremy Tregunna wrote: > On 06-09-14, at 15:27, oliver oli wrote: > >> Jeremy Tregunna wrote: >>> On 06-09-13, at 16:04, oliver oli wrote: >>> >>>> hi, >>>> >>>> i compiled Io from the darcs repository. It segfaults imediatly. Any >>>> idea what could be wrong? It's running on Debian (Etch) amd64. >>>> >>>> # make install >>>> [...] >;>>> # ldconfig >>>;> # io >>>> Segmentation fault >;>> Please fire up io in gdb, and execute the 'run' command. When it >>> crashes, get an output of the call stack ("bt full") and post it to >>> the mailing list. This will help us help you more. >;> i'm not familiar with gdb, i hope this helps... >> >> (gdb) run io >> Starting program: /usr/local/bin/io io >> >>; Program received signal SIGSEGV, Segmentation fault. >> 0x00002ae7ebbbaae7 in Coro_StartWithArg () from /usr/local/lib/ >> libiovmall.so >> (gdb) bt full >> #0 0x00002ae7ebbbaae7 in Coro_StartWithArg () >> from /usr/local/lib/libiovmall.so >> No symbol table info available. >> #1 0x00002ae7ebd49960 in swapcontext () from /lib/libc.so.6 >> No symbol table info available. >> #2 0x0000000000000000 in ?? () >> No symbol table info available. >> (gdb) >; > That's not really helpful yet. Could you edit the toplevel > Makefile.lib and find "OPTIMIZE". Change that to read: >; > OPTIMIZE := -Os -g -fPIC >; > Then make clean, and do a fresh build. Then try this again, showing > us the results of the full call stack. > > Sorry, I should have made sure you had debugging flags on initially. i compiled with the -g parameter, but it makes no difference to the gdb backtrace. i made a make uninstall and rebuilt io from a fresh archive (9-13 tarball). nothing changed, very strange. __._,_.___ Messages in this topic (6) Reply (via web post) \| Start a new topic . __,_._,___
segmentation fault
	2006-09-15 08:13:37

Jeremy Tregunna wrote: > On 06-09-14, at 15:27, oliver oli wrote: > >> Jeremy Tregunna wrote: >>> On 06-09-13, at 16:04, oliver oli wrote: >>> >>>> hi, >>>> >>>> i compiled Io from the darcs repository. It segfaults imediatly. Any >>>> idea what could be wrong? It's running on Debian (Etch) amd64. >>>> >>>> # make install >>>> [...] >;>>> # ldconfig >>>;> # io >>>> Segmentation fault >;>> Please fire up io in gdb, and execute the 'run' command. When it >>> crashes, get an output of the call stack ("bt full") and post it to >>> the mailing list. This will help us help you more. >;> i'm not familiar with gdb, i hope this helps... >> >> (gdb) run io >> Starting program: /usr/local/bin/io io >> >>; Program received signal SIGSEGV, Segmentation fault. >> 0x00002ae7ebbbaae7 in Coro_StartWithArg () from /usr/local/lib/ >> libiovmall.so >> (gdb) bt full >> #0 0x00002ae7ebbbaae7 in Coro_StartWithArg () >> from /usr/local/lib/libiovmall.so >> No symbol table info available. >> #1 0x00002ae7ebd49960 in swapcontext () from /lib/libc.so.6 >> No symbol table info available. >> #2 0x0000000000000000 in ?? () >> No symbol table info available. >> (gdb) >; > That's not really helpful yet. Could you edit the toplevel > Makefile.lib and find "OPTIMIZE". Change that to read: >; > OPTIMIZE := -Os -g -fPIC >; > Then make clean, and do a fresh build. Then try this again, showing > us the results of the full call stack. > > Sorry, I should have made sure you had debugging flags on initially. i compiled with the -g parameter, but it makes no difference to the gdb backtrace. i made a make uninstall and rebuilt io from a fresh archive (9-13 tarball). nothing changed, very strange. __._,_.___ Messages in this topic (6) Reply (via web post) \| Start a new topic . __,_._,___
segmentation fault
	2006-09-15 08:13:37

Jeremy Tregunna wrote: > On 06-09-14, at 15:27, oliver oli wrote: > >> Jeremy Tregunna wrote: >>> On 06-09-13, at 16:04, oliver oli wrote: >>> >>>> hi, >>>> >>>> i compiled Io from the darcs repository. It segfaults imediatly. Any >>>> idea what could be wrong? It's running on Debian (Etch) amd64. >>>> >>>> # make install >>>> [...] >;>>> # ldconfig >>>;> # io >>>> Segmentation fault >;>> Please fire up io in gdb, and execute the 'run' command. When it >>> crashes, get an output of the call stack ("bt full") and post it to >>> the mailing list. This will help us help you more. >;> i'm not familiar with gdb, i hope this helps... >> >> (gdb) run io >> Starting program: /usr/local/bin/io io >> >>; Program received signal SIGSEGV, Segmentation fault. >> 0x00002ae7ebbbaae7 in Coro_StartWithArg () from /usr/local/lib/ >> libiovmall.so >> (gdb) bt full >> #0 0x00002ae7ebbbaae7 in Coro_StartWithArg () >> from /usr/local/lib/libiovmall.so >> No symbol table info available. >> #1 0x00002ae7ebd49960 in swapcontext () from /lib/libc.so.6 >> No symbol table info available. >> #2 0x0000000000000000 in ?? () >> No symbol table info available. >> (gdb) >; > That's not really helpful yet. Could you edit the toplevel > Makefile.lib and find "OPTIMIZE". Change that to read: >; > OPTIMIZE := -Os -g -fPIC >; > Then make clean, and do a fresh build. Then try this again, showing > us the results of the full call stack. > > Sorry, I should have made sure you had debugging flags on initially. i compiled with the -g parameter, but it makes no difference to the gdb backtrace. i made a make uninstall and rebuilt io from a fresh archive (9-13 tarball). nothing changed, very strange. __._,_.___ Messages in this topic (6) Reply (via web post) \| Start a new topic . __,_._,___
segmentation fault
	2006-09-15 08:13:37

Jeremy Tregunna wrote: > On 06-09-14, at 15:27, oliver oli wrote: > >> Jeremy Tregunna wrote: >>> On 06-09-13, at 16:04, oliver oli wrote: >>> >>>> hi, >>>> >>>> i compiled Io from the darcs repository. It segfaults imediatly. Any >>>> idea what could be wrong? It's running on Debian (Etch) amd64. >>>> >>>> # make install >>>> [...] >;>>> # ldconfig >>>;> # io >>>> Segmentation fault >;>> Please fire up io in gdb, and execute the 'run' command. When it >>> crashes, get an output of the call stack ("bt full") and post it to >>> the mailing list. This will help us help you more. >;> i'm not familiar with gdb, i hope this helps... >> >> (gdb) run io >> Starting program: /usr/local/bin/io io >> >>; Program received signal SIGSEGV, Segmentation fault. >> 0x00002ae7ebbbaae7 in Coro_StartWithArg () from /usr/local/lib/ >> libiovmall.so >> (gdb) bt full >> #0 0x00002ae7ebbbaae7 in Coro_StartWithArg () >> from /usr/local/lib/libiovmall.so >> No symbol table info available. >> #1 0x00002ae7ebd49960 in swapcontext () from /lib/libc.so.6 >> No symbol table info available. >> #2 0x0000000000000000 in ?? () >> No symbol table info available. >> (gdb) >; > That's not really helpful yet. Could you edit the toplevel > Makefile.lib and find "OPTIMIZE". Change that to read: >; > OPTIMIZE := -Os -g -fPIC >; > Then make clean, and do a fresh build. Then try this again, showing > us the results of the full call stack. > > Sorry, I should have made sure you had debugging flags on initially. i compiled with the -g parameter, but it makes no difference to the gdb backtrace. i made a make uninstall and rebuilt io from a fresh archive (9-13 tarball). nothing changed, very strange. __._,_.___ Messages in this topic (6) Reply (via web post) \| Start a new topic . __,_._,___

[1-6]

about | contact Other archives ( Real Estate discussion Medical topics )