00:00:00 --- log: started forth/12.03.14 01:16:14 --- quit: MrBusiness (Quit: Leaving) 01:53:25 --- quit: ttmrichter (Ping timeout: 272 seconds) 03:13:36 --- join: ttmrichter (~ttmrichte@113.106.101.46) joined #forth 03:13:36 --- mode: ChanServ set +v ttmrichter 03:26:00 --- quit: DocPlatypus (Remote host closed the connection) 04:02:43 --- join: DocPlatypus (~skquinn@108-75-59-67.lightspeed.hstntx.sbcglobal.net) joined #forth 04:02:43 --- mode: ChanServ set +v DocPlatypus 04:07:04 --- quit: ttmrichter (Read error: Connection reset by peer) 04:32:41 --- join: ncv (~quassel@89.123.62.118) joined #forth 04:32:41 --- quit: ncv (Changing host) 04:32:41 --- join: ncv (~quassel@unaffiliated/neceve) joined #forth 04:32:41 --- mode: ChanServ set +v ncv 04:45:31 --- join: ttmrichter (~ttmrichte@221.234.38.23) joined #forth 04:45:31 --- mode: ChanServ set +v ttmrichter 05:19:27 --- quit: ncv (Ping timeout: 244 seconds) 07:31:52 --- join: Kumul (~Kumul@66-50-178-117.prtc.net) joined #forth 07:31:52 --- mode: ChanServ set +v Kumul 08:02:13 --- quit: mark4 (Quit: leaving) 08:45:17 --- quit: ttmrichter (Read error: Operation timed out) 08:46:31 --- join: ttmrichter (~ttmrichte@61.184.205.206) joined #forth 08:46:31 --- mode: ChanServ set +v ttmrichter 10:22:26 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 10:22:27 --- mode: ChanServ set +v MayDaniel 10:25:58 --- join: ncv (~quassel@89.123.62.118) joined #forth 10:25:58 --- quit: ncv (Changing host) 10:25:58 --- join: ncv (~quassel@unaffiliated/neceve) joined #forth 10:25:58 --- mode: ChanServ set +v ncv 10:37:45 --- quit: MayDaniel () 11:14:02 --- quit: ncv (Ping timeout: 260 seconds) 12:32:12 --- join: ncv (~quassel@unaffiliated/neceve) joined #forth 12:32:12 --- mode: ChanServ set +v ncv 13:12:37 --- join: mark4 (~mark4@24-183-5-217.dhcp.fdul.wi.charter.com) joined #forth 13:12:38 --- mode: ChanServ set +v mark4 13:12:57 blah no tathi dangit 13:55:05 --- join: nighty^ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 13:55:06 --- mode: ChanServ set +v nighty^ 14:13:47 --- join: ncv_ (~quassel@89.123.7.245) joined #forth 14:13:48 --- mode: ChanServ set +v ncv_ 14:14:41 --- quit: ncv (Ping timeout: 245 seconds) 15:26:48 --- quit: ncv_ (Ping timeout: 255 seconds) 15:42:26 --- join: tschak_ (~tschak@pool-96-226-11-78.dllstx.fios.verizon.net) joined #forth 15:42:26 --- mode: ChanServ set +v tschak_ 15:44:42 --- quit: tschak (Ping timeout: 260 seconds) 15:53:08 --- join: tathi (~josh@dsl-216-227-97-239.fairpoint.net) joined #forth 15:53:09 --- mode: ChanServ set +v tathi 15:54:55 --- join: I440r (~zhiming@173-167-173-233-illinois.hfc.comcastbusiness.net) joined #forth 15:54:55 --- mode: ChanServ set +v I440r 15:55:02 tathi! 15:55:10 i need help lol 15:56:12 --- quit: Kumul (Remote host closed the connection) 15:58:05 --- join: MrBusiness (~MrBusines@184.99.7.19) joined #forth 15:58:06 --- mode: ChanServ set +v MrBusiness 16:02:21 --- join: Kumul (~Kumul@66-50-178-117.prtc.net) joined #forth 16:02:21 --- mode: ChanServ set +v Kumul 16:08:36 Oh? 16:08:40 yea 16:08:57 i did major surgery on the elf stuff in fsave 16:09:02 something aint working right 16:09:26 readelf -a looks fine but ./isforth segfaults somewhere in the header relocation 16:09:42 kernel.com does not 16:10:14 This checked in? 16:10:19 yes 16:11:01 Huh. kernel.com segfaults for me. 16:11:11 Oh, I didn't turn randomization off, hang on. 16:11:11 rebuilt? 16:11:15 no 16:11:15 yup 16:11:20 randomization should be fine with it 16:11:34 strace it. does it fault before the process is started? 16:11:56 did u update the kernel sources and the extensons? 16:12:54 Yeah, looks like it does segfault before it starts. 16:13:08 what does readelf -a show on kernel.com? 16:13:39 any clues? 16:15:22 http://pastebin.com/9rNV7qsx 16:16:24 ok what system are u building this on? 16:16:51 its not putting pax flags in there 16:17:02 so u only have 2 program headers 16:17:04 i get 3 16:17:54 Old debian 16:19:22 ok so make clean && make produced a kerenel.com that barfs? 16:20:14 Huh. that bss stuff looks screwy. 16:20:31 im just createing 1 meg of bss 16:20:37 not 1 meg minus .text size 16:20:44 im cheating on the kernel a bit 16:21:33 Yeah, but look, the virtual and physical addresses in the program header are different. 16:21:42 don't even match alignments. 16:21:43 etf 16:21:45 wtf 16:21:45 yea 16:21:50 thats messed up 16:22:00 LOAD 0x004250 0x0804c250 0x0804c249 0x00000 0x100000 RW 0x1000 16:22:06 tho that is mine 16:22:16 And the offset doesn't match the address either. 16:22:34 offset is offset within the file 16:23:02 which is page aligned to the page following the one where .text ends 16:26:16 i dont undertand why kernel.com doesnt run on ur system 16:26:23 out of memory? 16:27:22 u imposing limits? 16:28:31 That doesn't look like a valid ELF to me. 16:28:41 its what nasm produced 16:28:49 I think it's the linker. 16:28:59 oh 16:29:13 ther a linker script in the kernel source tree now too 16:29:18 Yeah, I saw that. 16:29:27 Why are you hard-coding the address? 16:29:45 .bss 0x804c250 : AT(ADDR(.text) + SIZEOF(.text)) ALIGN(1) { *(.bss) } 16:29:45 because i have to guarantee that bss is contiguous with .text 16:30:09 So you have to update the linker script every time you add or remove code from the kernel? 16:30:10 its a kludge 16:30:17 yes its a kludge 16:30:19 OK. 16:30:30 ./extend is not subject to it :) 16:31:31 Well, the value in your ldscript is not the value I'm getting. 16:31:40 If I change it to match then kernel.com runs. 16:31:49 wtf 16:31:50 ok 16:31:57 well its temporary 16:32:02 look at ./extend 16:32:16 and readelf -a isforth 16:32:17 thres something fscked up with it 16:32:28 oooihhhhhhhh 16:32:32 YOUR header is 0x20 bytes smaller than mine 16:32:44 i bet ur hard coed address was 0x20 bytes earlier in memory too 16:33:02 no, 0x90. 16:33:12 Er...wait. 16:34:03 0x5a 16:34:08 Dunno why. 16:34:30 0x5a is decimal 90 is it not? 16:35:10 but ok... u can ./extend at least 16:36:16 yes 16:36:45 more thought needs to go into that linker script maybe but its a temporary hack 16:38:25 tho to fix i could set ORG in isforth.asm for the .text section 16:40:37 So why do you think there's something wrong with isforth's ELF headers? 16:41:06 run ./isforth 16:43:58 And? 16:44:12 it segfaults yes? 16:44:18 Yes. 16:44:33 why does isforth gpf and kernel.com doesnt 16:44:42 has to be the way fsave is creating the executable 18:08:41 --- quit: tathi (Quit: leaving) 18:21:44 --- quit: nighty^ (Read error: Connection reset by peer) 18:41:05 --- join: nighty^ (~nighty@69-165-220-105.dsl.teksavvy.com) joined #forth 18:41:06 --- mode: ChanServ set +v nighty^ 19:04:50 --- join: Snoopy_1711 (Snoopy_161@dslb-088-069-140-130.pools.arcor-ip.net) joined #forth 19:04:51 --- mode: ChanServ set +v Snoopy_1711 19:06:52 --- quit: Snoopy_1611 (Ping timeout: 265 seconds) 19:27:56 --- quit: ASau (Ping timeout: 260 seconds) 19:50:14 --- join: ttmrichter_ (~ttmrichte@221.234.38.23) joined #forth 19:50:14 --- mode: ChanServ set +v ttmrichter_ 19:50:36 --- quit: ttmrichter (Disconnected by services) 19:50:44 --- nick: ttmrichter_ -> ttmrichter 22:59:04 --- quit: Kumul (Quit: gone) 23:25:41 * tschak_ is having fun figuiring out how to revector words in fig-forth 23:25:53 just changing the CFA isn't working..hehehe 23:49:37 of what? 23:49:43 oh 23:49:53 ' foo is bar ??? :) 23:50:08 or use ;uses 23:50:40 to change word BLUE to execute red instead, I was trying: 23:50:57 ' RED CFA ' BLUE CFA ! 23:51:00 what kinds of words are blue and red? 23:51:11 colon defs? 23:51:13 : RED 67 710 C! ; 23:51:14 yes 23:51:37 i'm practicing to get ready to re-vector ABORT 23:51:40 is your fig forth direct or indirect threaded? 23:51:44 indirect. 23:51:59 thats what i thought 23:51:59 it is literally the ragsdale 6502 forth 23:52:03 ern 23:52:11 oh ya u said the other day 23:52:12 hrm 23:52:24 i'm literally using the original source code listing as a basic reference 23:52:31 ok so with this forth what is at the CFA of a word? 23:52:47 in isforth which is direct threaded the CFA is a call to nest 23:52:48 CFA is literally PFA - 2 23:52:58 ok so cfa is a pointer 23:53:02 to nest? 23:53:08 let me see 23:55:38 DOCOL 23:55:51 yea 23:56:04 docol is docolon which is basically the same as my nest 23:56:11 ok well you might have to create a new primative 23:56:26 hrm actually im not sure what your trying to do is possibke 23:56:29 possible 23:56:40 wait, it damn well should be! 23:56:49 ok so 23:57:00 i've seen screens in other atari forths that patch ABORT 23:57:01 and 23:57:06 you have two colon definitions and you want to make one run the other 23:57:27 if you look in the 6502 forth code, there literally are forward CREATE definitions that get vectors attached to them in later screens 23:57:34 --- join: ncv (~quassel@unaffiliated/neceve) joined #forth 23:57:34 --- mode: ChanServ set +v ncv 23:57:39 replace one colon definition with another 23:57:46 ok lets examine how a colon definiton works 23:58:07 when you execute RED the address at CFA is fetched and jumped to 23:58:15 so you end up running DOCOL 23:58:33 mhm, and I can literally do ' RED CFA EXECUTE 23:58:51 docol takes the address of the CFA of the word that jumped to it, adds 2 to it and puts that in the interprative pointer 23:59:36 ok it CAN be done 23:59:52 nothing is impossible but what you might have to do is revector RED to point to something other than DOCOL 23:59:59 --- log: ended forth/12.03.14