@kas1e

Awesome!

I managed to get a clib2-ified build going avoiding some of the hacking. The config.h in libiberty was getting wrong values for clib2 which meant that it was trying to get alloca.h, process.h, etc. The __USE_CLIB2_TIMEVAL define removes the need to edit the sys/select.h file and I don't get the cast problems


1. ../configure --host=ppc-amigaos --target=ppc-amigaos --build=x86_64 --disable-nls --disable-werror --disable-sim CFLAGS="$CFLAGS -mcrt=clib2 -D__USE_CLIB2_TIMEVAL=1" LDFLAGS="$LDFLAGS -L/home/billy/Projects/amiga-gdb/ -lnet -lunix"

2. cd libiberty

3. patch < config.patch

4. cd ..

5. make

But my clib2 is causing me problems on the final linking of gdb with a missing getpgrp so I need to add that to the linking

However if I can't get the clib2 version to fully build, and given that it works on your set up, it's going to be that I'm missing something on my clib2 installation, I can still build the newlib version fine so I can work on both issues there hopefully.

@kas1e

Cheers ok that makes sense to my slow brain now So clib2 is hopefully the way to go. I found that to be the case with simplegit too when it comes to Posix compatibility.

Finally(!) on my amiga, and if I run gdb 7.5.1 on a simple hello_world program with


gdb helloworld


I get a grim reaper pointing at bfd_check_format_matches+ 0.210 (section 1 @0x230EC0) which ties in with my first guess of where the seek bug is that we need to fix.

@kas1e

So that is coming from exec_file_attach (), lin2 252 in gdb/exec.c, I'm guessing. It may not be a seek problem, but the code to check might be bfd_check_format_matches() in bfd/format.c.

Just to clarify, if you run

objdump -g helloworld

does it work?



It's me being slow, so apologies for this, but are you saying that you are getting that error for both clib2 and newlib on 7.5.1? And for 6.3,it works for clib2 but not newlib?


Hopefully be on my amiga in a couple of hours to check this too, but it looks like clib2 might be the way to go then.

@kas1e

Well found! Looking at the code, it looks like that gdb_select (), which is calling posix select () in posix_hdep.c, and that is returning -1. I'll add some debug messages to see what error is actually happening.

If the problem doesn't occur when we use gdb with a filename on the command line, then it won't affect how gdb is mostly used I guess.

@kas1e

I'm not at my amiga right now, so my dodgy memory might get this wrong. On linux, for the program that you're trying to debug, say it's called foobar, run

objdump -g foobar

and look for the part after "Contents of the .debug_info section:"

The DW_AT_name and DW_AT_comp_dir fields should be filled in for the DW_AT_compile_unit section and give the name of the source file and the directory that it is in respectively.

This is what gdb is looking for on linux at least.

Does the amiga program that you're running gdb with have these parts filled in? If so, we will at least know that the info is in the right place.

Tomorrow I should be able to get on my amiga and look properly rather than having to guess!

@kas1e

For my use cases, which generally are load up a program and step through until it crashes, there wasn't any extra functionality that I needed from the later version. Gdb 10 feels a bit faster at parsing the symbols when debugging shared objects, but that was only really noticeable to me when debugging a Qt program. By the looks of the changelog, they did that by using threading. You have way more experience of threading issues on OS4 so you will have a better idea than me as to if that is a pain worth taking 🙂

So, for me personally, any version on OS4 would do other people might need the newer features, I just want a debugger that we can use 🙂

@kas1e


Glad to be a rule breaker I'm sure there are loads of changes but when I went from gdb 7.x up to 10.1, the only change I noticed was that font styles and colours were implemented for the source code when you are using gdb. Looking at the changelog, that was implemented in 8.3

@kas1e

Awesome work! I can get it to build too now, I had to slightly tweak it to get it see the termcap library, but that is just down to where people have put it. So I used



I'll get on to my X1000 in the next couple of days and start testing it out and start working on the issues that you mentioned.

@kas1e


This is great, thanks Roman. I've checked out the repo and on Linux Mint 19.3, which is based on Ubuntu 18.04, and I am missing the termcap library which gives tgetent so I get to



Has your build got past this part? libncurses5-dev and readline-dev don't fix this for me so I'll download the termcap library from the GNU site and build and add it to this.

@walkero

Yup, a repo will make this easier with all of the code in one place. I'm happy to help out with any programming that we need to do to get this working. Kas1e, can you create a repo with the 7.5.1 code with the needed patches in?

Hi all

Following on from the chat at
https://www.amigans.net/modules/xforum ... id=123203#forumpost123203, I've tried to get the simplegit and libgit2 work that I'd done into a state so other people might be able to help out too. The repos are at

https://github.com/billyfish/simplegit

and

https://github.com/billyfish/libgit2/tree/amigaos4_port

The additional instructions for how to set it up with my changes are at https://github.com/billyfish/simplegit/blob/master/build.md.

The piece of work that needs to be done next is how to implement mmap () and munmap (). My memory of this is a bit hazy but I think that there are only one or two times where mmap () is used to write to a file and I was checking if they used in a threaded situation or whether we could assume only one thread using it a time which would again make it easier.

Basically if anyone wants to get involved, you're very welcome!

billy

@sTix

Quote:

I started work on upgrading to the latest libgit2, and got it using AmiSSL rather than a static older version of OpenSSL, but I stopped when I hit the fact the it uses mmap () and munmap () now. I think there was only one or two instances where it was writing to a mmap'd buffer, the rest were just reading which is obviously easier to deal with. My build environment could use the older libgit2 or a newer one so I'm going to update the instructions on my forked repo as how to build the different versions and see if I can get the energy to have another crack at it. Anyone willing to help work on it would be very appreciated!

@kas1e

I absolutely agree that gdb would be a game changer as development would be sooooo much easier with a working debugger.

@LiveForIt

Quote:

You might be right, but if it was integrated using an ARexx script that would make it more user-friendly. I think if the conversion option was there, we'd see how much it would be used.

Quote:

In Final Writer, at least, you can already do this. I've got an ARexx script that prints to postscript and then converts it to PDF.

@jabirulo

Thanks, yeah it was my mistake. Every time I go back to coding something using Reaction instead of MUI, I forget to add the GA_RelVerify tags as I've been used to doing everything using IDoMethod () calls and subclassing, so my bad! I suppose I could do the same thing in Reaction but I just tend to follow the style of the Reaction examples where they tend to have everything in the main message handling loop.

Cinnamon Writer looks promising to me. As for Final Writer, Wordworth, etc. In terms of functionality that I personally need, they already had enough. Other people might need more obviously. I thought that if they had the ability to import and export DOCX files, that would be enough for me. I always wondered about what it would take to write a converter program for final writer <-> docx but never really investigated it further

Hi

Following on from trixie's excellent advice at https://www.amigans.net/modules/xforum ... id=122939#forumpost122939 I've started building a program using the enhancer core classes. The toolbar gadget is great but I'm getting stuck with the listviewer gadget. The documentation, like my brain, is a bit sparse, so I thought that I'd ask here.

1. The gadget seems to create an extra unusable column to the right of the columns that you specify. This takes up extra space that could be used by the columns with data in and affect the minimum size of the window. If you look at https://photos.app.goo.gl/h8h3dsWX9rLPWYft5 you can see an extra column after the "comment" column in the 1st window and the one after the name of the image in the second one.

2. How do you react to the user selecting/activating an item in the list. I couldn't find any examples of this in the example programs and I couldn't get it to work with using WMHI_GADGETUP or something similar.


cheers

billy

@trixie

Awesome, thanks trixie. It's convinced me to use your toolbar gadget for the next program that I'm currently working on, I know who to ask for help

@kas1e

-fsigned-char should do it for you in GCC.

@derfs

Quote:

lol, this made me laugh, sorry Derfs