| |
| |
| |
|
Page: 1 2 3
Comments:
<0> can i say to gcc to put the string at the end of the file ?
<0> can someone explain me what does mean *(.data) in this block of ld script ?
<0> .rdata : {
<0> *(.data)
<0> }
<0> ?
<1> hmm
<0> i do something wrong ?
<1> essentially, it tells ld to put the ".data" sections from all ("*") objects into the .rdata section in the output
<1> that is generally considered a bad idea, yes
<0> lol
<0> ok
<1> .rdata is for read-only data, such as strings, while .data is for modifiable data
<0> ok
<0> think a lot
<1> depending on your setup, it may work, or not.
<0> stupid question: I witch case the ***ociation must be different of text to text data to data rdata to rdata ... etc ?
<1> for example, on uClinux with shared executable support, you only have a single copy of the .text and .rodata sections, but one copy of .data per instance
<1> you can merge .text and .rodata without problems normally
<0> ok
<0> think for the light
<1> the sections basically say what the section is about, the linker then sorts stuff into "segments", which have attributes that tell what is allowed
<1> for example, .text is by default executable and read-only
<1> .rodata is not executable and read-only
<1> .data is not executable, and read-write
<0> ok great
<1> .bss is not executable, read-write and zero-initialized
<1> what each segment really means is defined in the linker script; these are the defaults
<1> you can also have additional sections if you tell the linker which type they should have
<0> yes i use the simple way (defalt) for the moment
<0> it's not easy to understand but
<0> it come into my brain slowly
<1> so normally you want a 1:1 mapping for the "standard" things (".text", ".data", ".rodata", ".bss")
<0> yes
<0> exactly
<0> rodata insted of rdata you preconize
<1> these names are system dependent
<1> a lot of systems have a lot more
<0> i try to build my own ;)
<0> my micro kernel
<1> hehe
<0> the probleme come from this remark
<1> I have an own microkernel too
<0> yes great
<0> it's advanced ? (not the correct word)
<0> what is it spef ?
<1> it's going to be used as the next generation bootloader for the picotux
<0> multitask ? premptif ?
<1> nope
<1> neither
<0> picotux ?
<0> i dont know what it is ?
<1> an embedded ARM system
<0> ok
<1> http://www.picotux.com/
<0> (quick google...)
<0> think
<0> more quick than google
<0> Wha hoo !
<1> basically, a microkernel does not do multitasking if it can avoid it
<1> you have a task for that. :-)
<0> :)
<1> a "true" microkernel is just message p***ing
<0> ho
<0> he !!! im .... a ...
<0> in the first picture
<0> on the home page
<1> yep
<0> it's a seria ethernet converter ?
<1> among other things
<1> it's an ARM box running uClinux
<1> 55 MHz
<0> O_O !!!!
<0> what is the dimension ?
<0> my big finger ?
<0> my hand ?
<0> a cigarette packet ?
<1> 19x19x36mm
<0> O_O
<0> wha f..k !
<0> great product
<1> you can guess from the size of the Ethernet plug
<0> picotux
<0> i remember
<1> well, I'm currently hacking the new bootloader
<0> let me read 2 minute you website
<0> (I very intersted, i programming on microship PIC
<0> it is you that sale this ?
<1> well, the company I work for does
<1> http://www.picotux.com/~richter/bootloader.ld is what I currently use as an ld script
<0> ok you are into technical departmeent or commercial ?
<1> technical
<0> What a Ld !
<1> basically, it's pretty simple
<0> i dont understand a lot
<1> there is a flash chip that's initially mapped to address 0 and repeated all over the place due to the high bits of the address being masked out
<0> ok
<0> what mean flash AT>flash ?
<0> ho yes
<0> i see at the top
<0> MEMORY
<0> great
<1> >flash means that the VMA is in the "flash" memory section, AT>flash means that the LMA is there too
<0> great
<1> if these are different it means that the code is stored in flash, then copied to ram by some other code and then executed from ram
<0> ok
<0> expect serial port
<1> .text.init sets up the ram, then copies .text.startup_copy to ram and jumps to it
<0> what king of port exist on your module ?
<1> serial and/or a set of GPIOs and of course Ethernet or wireless
<1> wireless is the reason for the new bootloader
<0> Picotux 100
<0> ok
<0> great
<0> arf, it's not ship !
<0> ;)
<1> of course
<0> it's never so ship
<0> great projet
<1> you haven't seen the 200 yet
<1> it's not finished so not published yet, but it comes with an MMU and a MMC-micro card slot
<1> and Debian preinstalled if you like
<0> warch
<0> great product
<0> my own system is a peanuts near yours !
<0> it's a little premptive multitask nano system for x86
<1> well, for the picotux 100 we bought the modules as that was cheaper; for the 200 we did the design ourselves
<1> ah
<1> well, if I can help, just ask
<0> think
<0> thanks
<1> a hint about testing: since I don't think you have a JTAG setup and everything, you might want to install Xen
<1> and, as a first step, implement a "hello world" thing that runs under Xen and outputs to the Xen console
<2> I'm getting this with the gcc from ubuntu edgy: mpdsong.cpp:107: internal compiler error: Segmentation fault
<2> and I'm asked to report a bug
<1> then you can do the good old printf() debugging as soon as you've implemented printf
<2> are there known problems with the compiler in edgy, or should I just go ahead?
<0> yes
<0> some cheap screens here
<0> http://www.hexanium.com/zumba/screen.htm
<1> Z_God, I ***ume you are using x86 architecture?
<2> yep
<1> Z_God, essentially, gcc exists in so many different variants that it is impossible to tell what variant has what bugs
<1> Z_God, is what you are compiling open source?
<2> k
<2> yes
<2> http://havtknut.tihlde.org/qmpdclient/download.html
<2> there is the download
<1> Z_God, can you make preprocessed source from the offending file?
<2> I'll try
<1> Z_God, i.e. run the compiler with a different output file and -E instead of -c?
Return to
#gcc
or
Go to some related
logs:
load deamon xscreensaver
#bash
#perl
mysql utf8_german
libggi2 kubuntu
Jeff Salesman
phprox
#physics
initrd powerpath
DBD-PG MakeMaker.pm 869
|
|