Who is responsible for Newlib/vbcc ?

Have a question about our Software Developer Kit? Ask them here.
zzd10h
Posts: 546
Joined: Sun Sep 16, 2012 5:40 am
Location: France

Re: Who is responsible for Newlib/vbcc ?

Post by zzd10h »

For my case, I still use gcc, no vbcc
http://apps.amistore.net/zTools
X1000 - AmigaOS 4.1.6 / 4.1 FE

xenic
Posts: 1164
Joined: Sun Jun 19, 2011 12:06 am

Re: Who is responsible for Newlib/vbcc ?

Post by xenic »

zzd10h wrote:For my case, I still use gcc, no vbcc
I should have directed my comment to phx since he was the one compiling with vbcc.
AmigaOne X1000 with 2GB memory - OS4.1 FE

blmara
Posts: 63
Joined: Thu Jun 23, 2011 9:03 am

Re: Who is responsible for Newlib/vbcc ?

Post by blmara »

xenic wrote:
zzd10h wrote:For my case, I still use gcc, no vbcc
I should have directed my comment to phx since he was the one compiling with vbcc.
Actually, I was the person compiling with VBCC and reported this elf message. Phx is the person updating the VBCC. If I understood correctly, Frank has located the problem to newlib (for example, launching AmiPDF generates this error message and also the message above indicates this is not a problem only for users of VBCC).

Marko

xenic
Posts: 1164
Joined: Sun Jun 19, 2011 12:06 am

Re: Who is responsible for Newlib/vbcc ?

Post by xenic »

blmara wrote:
xenic wrote:
zzd10h wrote:For my case, I still use gcc, no vbcc
I should have directed my comment to phx since he was the one compiling with vbcc.
Actually, I was the person compiling with VBCC and reported this elf message. Phx is the person updating the VBCC. If I understood correctly, Frank has located the problem to newlib (for example, launching AmiPDF generates this error message and also the message above indicates this is not a problem only for users of VBCC).

Marko
Pardon my confusion over who is who here. However, I tried running AmiPDF with Sashimi running and didn't see any messages. I even switched to the debug kernal, performed a cold reboot and still don't see any message in Sashimi when starting AmiPDF. Others have reported that they don't see the message either, so there must be something different about your system setup.
AmigaOne X1000 with 2GB memory - OS4.1 FE

User avatar
salass00
AmigaOS Core Developer
AmigaOS Core Developer
Posts: 516
Joined: Sat Jun 18, 2011 3:12 pm
Location: Finland
Contact:

Re: Who is responsible for Newlib/vbcc ?

Post by salass00 »

The issue with the startup.o file used by vbcc has just been fixed in the latest newlib beta version with some help from Frank Wille (AKA phx) who is the maintainer of the AmigaOS vbcc ports.

As said before the issue wasn't harmful in any way and only showed itself when debuglevel was set higher than zero, which it really it shouldn't be for most people. The pretty much only reason to have a debug level higher than zero is if you are debugging the kernel or some other system component which is affected by this setting. If you are not using it to debug system components then you're just making the OS slower for no real reason.

User avatar
ssolie
Beta Tester
Beta Tester
Posts: 1010
Joined: Mon Dec 20, 2010 8:51 pm
Location: Canada
Contact:

Re: Who is responsible for Newlib/vbcc ?

Post by ssolie »

blmara wrote:Really, are there people developing newlib.library?
The AmigaOS development team looks after all the components as a collective. There are various members that specialize in pieces of the OS but everyone is welcome and able to work on any component. There is not one person who is the newlib maintainer.

In this case, vbcc is a 3rd party compiler and we do not test with it. If something happens to break with vbcc for some reason we will try to work it out but it is not the officially supported compiler. GCC is the officially supported compiler and we always test with that one.
ExecSG Team Lead

blmara
Posts: 63
Joined: Thu Jun 23, 2011 9:03 am

Re: Who is responsible for Newlib/vbcc ?

Post by blmara »

salass00 wrote:The issue with the startup.o file used by vbcc has just been fixed in the latest newlib beta version with some help from Frank Wille (AKA phx) who is the maintainer of the AmigaOS vbcc ports.

As said before the issue wasn't harmful in any way and only showed itself when debuglevel was set higher than zero, which it really it shouldn't be for most people. The pretty much only reason to have a debug level higher than zero is if you are debugging the kernel or some other system component which is affected by this setting. If you are not using it to debug system components then you're just making the OS slower for no real reason.
Great to hear both that the reason for this issues was found and it wasn't actually harmful. Thanks!

Marko

User avatar
Raziel
Posts: 927
Joined: Sat Jun 18, 2011 4:00 pm
Location: a dying planet

Re: Who is responsible for Newlib/vbcc ?

Post by Raziel »

salass00 wrote:The issue with the startup.o file used by vbcc has just been fixed in the latest newlib beta version with some help from Frank Wille (AKA phx) who is the maintainer of the AmigaOS vbcc ports.

As said before the issue wasn't harmful in any way and only showed itself when debuglevel was set higher than zero, which it really it shouldn't be for most people. The pretty much only reason to have a debug level higher than zero is if you are debugging the kernel or some other system component which is affected by this setting. If you are not using it to debug system components then you're just making the OS slower for no real reason.
So, "SERIAL MUNGE DEBUGLEVEL=5" does not help debugging problems in programs but only helps debugging stuff in OS components and kernel?

Can i savely delete this parts then or should i keep MUNGE?
People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg

blmara
Posts: 63
Joined: Thu Jun 23, 2011 9:03 am

Re: Who is responsible for Newlib/vbcc ?

Post by blmara »

ssolie wrote:...
In this case, vbcc is a 3rd party compiler and we do not test with it. If something happens to break with vbcc for some reason we will try to work it out but it is not the officially supported compiler. GCC is the officially supported compiler and we always test with that one.
Yes, I know and I am happy that you have helped to solve the issue even if the compiler is not the official one.

Marko

User avatar
tonyw
AmigaOS Core Developer
AmigaOS Core Developer
Posts: 1410
Joined: Wed Mar 09, 2011 1:36 pm
Location: Sydney, Australia

Re: Who is responsible for Newlib/vbcc ?

Post by tonyw »

"SERIAL MUNGE DEBUGLEVEL=5" does not help debugging problems in programs but only helps debugging stuff in OS components and kernel?
Certainly not! Using the "debug" kernel is essential if you are doing any sort of program debugging - OS components or otherwise.

"Serial" means print debug information such as output from the IExec->DebugPrintF() function directly to the serial port. If you are debugging a system component you need to do this because if there is a crash, it will help get all the information printed. Using printf() or a debugger likely will prevent the last line or two from appearing.

"Munge" is not essential but does make it more likely that a program that forgets to initialise its memory will fail.

"DebugLevel=5" is rather extreme and won't help you debug anything except the inner-most parts of the OS. Leave it at "1" to get the minimum debug output from the kernel, I/O drivers and DOS.

So if you are debugging software (any software), make sure you use the debug kernel and "Serial Munge DebugLevel=1". If you are not debugging or testing anything, use the normal kernel and debug level "0".
cheers
tony

Post Reply