Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
91 user(s) are online (72 user(s) are browsing Forums)

Members: 1
Guests: 90

Arthas, more...

Support us!

Headlines




« 1 ... 4 5 6 (7) 8 »


Re: GDB
Just popping in
Joined:
2011/7/20 20:01
From In the sticks
Posts: 172
@kas1e

Ah good spot, I'd started going down the path of tidying up the 6.3 version but Alfkil's Spotless one looks nicer, using APIs like IMMU->GetPhysicalAddress() rather than doing the relocation stuff by hand. I'll copy/steal that idea

   Report Go to top

Re: GDB
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 7022
@billifish
When I talked with Alfkil a few weeks ago about all sort of things, he says that he coded Spotless exactly for the reasons people can "steal" his code in "normal" debuggers :) So I am sure he will be more than happy to know that things back to the GDB in end :)

And we basically better to refer to SpotLess with stealing all other ideas, as Alfkil spend quite a lot of time with all this, and do all probably in most proper for today realms way (and he was in contact with kernel devs, so surely he's code is one to refer).


Btw, related to the x5000 issue with old GDB when we set a breakpoint and then instead of a break, we catch a "SIGBUS signal, bus error". I enabled debug in old-working-on-other-platforms GDB, and that the output we had on x5000:

(gdb) break 2
break 2
Breakpoint 1 at 0x7f20344c
file test.cline 2.
(gdbr
r
Starting program
Work:aa/test_dwarf2 
target_xfer_memory 
(0x7f20344cxxx4readxxx) = 4bytes =
 
94 21 ff f0
target_xfer_memory 
(0x7f20344cxxx4writexxx) = 4bytes 7d 82 10 08
target_insert_breakpoint 
(0x7f20344cxxx) = 0
target_fetch_registers 
(pc) = 00000000 0x0 0
target_terminal_inferior 
()
target_resume (-1, continue, 0)
target_wait (-1status) = 1640258176,   status->kind stoppedsignal SIGBUS
target_fetch_registers 
(pc) = 023aecf0 0x23aecf0 37416176
target_terminal_ours_for_output 
()

Program received signal SIGBUSBus error.
target_xfer_memory (0x7f20344cxxx4writexxx) = 4bytes =
 
94 21 ff f0
target_remove_breakpoint 
(0x7f20344cxxx) = 0
target_terminal_ours 
()
target_fetch_registers (r1) = 02247f90 0x2247f90 35946384
0x023aecf0 in 
?? ()
target_create_inferior (Work:aa/test_dwarf2, , xxx1)
(
gdb)


And on Pegasos2 (where it works still, with the same latest aos4 + update2, etc):

(gdb) break 2
break 2
Breakpoint 1 at 0x7fcf844c
file test.cline 2.
(gdbr
r
Starting program
RAM Disk:test_dwarf2 
target_xfer_memory 
(0x7fcf844cxxx4readxxx) = 4bytes =
 
94 21 ff f0
target_xfer_memory 
(0x7fcf844cxxx4writexxx) = 4bytes 7d 82 10 08
target_insert_breakpoint 
(0x7fcf844cxxx) = 0
target_fetch_registers 
(pc) = 00000000 0x0 0
target_terminal_inferior 
()
target_resume (-1, continue, 0)
target_wait (-1status) = 1750208704,   status->kind stoppedsignal SIGTRAP
target_fetch_registers 
(pc) = 7fcf844c 0x7fcf844c 2144306252
target_xfer_memory 
(0x7fcf844cxxx4writexxx) = 4bytes =
 
94 21 ff f0
target_remove_breakpoint 
(0x7fcf844cxxx) = 0
target_terminal_ours 
()

target_fetch_registers (r1) = 65341d10 0x65341d10 1697914128
Breakpoint 1
main () at test.c:3
3    
{
target_create_inferior (RAM Disk:test_dwarf2, , xxx1)
Current language:  autocurrently minimal
(gdb)


See, in target_wait() , x5k received "signal = SIGBUS" while on peg2 we receive there "signal = SIGTRAP". Also on x5k status = 1640258176, while on peg2 status = 1750208704 whatever it means ..

So what did it means at all :)? That on x5k signals messed up? Probably we can find out the answer after breakpoint_insert added, then we can add printfs to signals handling to see wtf happens. I very much hope it will be possible to work around it without the need for fixes in the kernel.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: GDB
Just can't stay away
Joined:
2006/12/1 18:01
From Copenhagen, Denmark
Posts: 1238
@kas1e

Quote:
Also on x5k status = 1640258176, while on peg2 status = 1750208704 whatever it means ..
Those numbers look like pointers to me, what happens if you dereference them?

Best regards,

Niels

   Report Go to top

Re: GDB
Just popping in
Joined:
2011/7/20 20:01
From In the sticks
Posts: 172
@kas1e

Seein target_wait() , x5k received "signal = SIGBUS" while on peg2 we receive there "signal = SIGTRAP"Also on x5k status 1640258176, while on peg2 status 1750208704 whatever it means ..

So what did it means at all :)? That on x5k signals messed upProbably we can find out the answer after breakpoint_insert addedthen we can add printfs to signals handling to see wtf happensI very muych hope it will be possible to work around it without the need for fixes in the kernel.


Could well be. Once I've got the debug hook and breakpoint code in which will be pretty quick to do, it's just finding the time, then we can see. The trap_to_signal () function may need to be adapted for the x5000 possibly.

   Report Go to top

Re: GDB
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 7022
@billyfish
Damn, was in hope you were already done with when found that you answer in the topic :) Hope it will not take long, monitoring that topic and your github acc every day.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: GDB
Just popping in
Joined:
2011/7/20 20:01
From In the sticks
Posts: 172
@kas1e

Sorry for the hold up Roman

I can't currently get on my amiga to test whether it works but I've uploaded a version with some "possible working" breakpoint code in there I've tried to integrate what Aflkil does in Spotless.

Once I've got a new hard drive in there I'll be able to boot up my amiga and check whether it actually works!


   Report Go to top

Re: GDB
Quite a regular
Joined:
2007/2/6 13:57
From Donostia (SPAIN)
Posts: 632
Hi, what attribs/tags do I need to add to compile a simple helloworld.c so it can be used with your GDB?

Now I use: ppc-amigaos-gcc helloworld.c -o helloworld -gstabs -Wall

'cos I get:
#SDK:C/gdb helloworld
_initialize_amigaos_nat
[New inferior 0]
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "ppc-amigaos".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /Devel/SDK/ejemplos/helloworld...target_terminal_ours ()
I'm sorry, Dave, I can't do that. Symbol format `elf32-amiga' unknown.
(gdb) quit
quit
target_close (1)
target_close (0)
#

   Report Go to top

Re: GDB
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 7022
@jabirulo
-gstabs

@billyfish
Nice! Will try it out soon

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: GDB
Quite a regular
Joined:
2007/2/6 13:57
From Donostia (SPAIN)
Posts: 632
@kas1e

Allready using -gstabs option, but when tryng ot laod the exec into GDB:

..
I'm sorry, Dave, I can't do that. Symbol format `elf32-amiga' unknown.
...

I did a gihub clone of gdb751 and followed steps to (used cygwin) build GDB, maybe I mssing some important step ¿:-/

my system is a SAM460ex.

   Report Go to top

Re: GDB
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 7022
@javier
You tried my one, or latest from billyfish ?

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: GDB
Quite a regular
Joined:
2007/2/6 13:57
From Donostia (SPAIN)
Posts: 632
@kas1e

from billyfish github repo with changes from this week.

   Report Go to top

Re: GDB
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 7022
@jabirulo
I will be at home tomorrow so can check, but at first, you may try the previous commit from billfish's repo which 100% works for loading binaries.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: GDB
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 7022
@jabirulo
Tested latest commits from billifish : all build fine, i can load binary on both x5000 and peg2. There is prebuild version, try it: http://kas1e.mikendezign.com/aos4/gdb/gdb_751_commit_43.zip

@billyfish
Tried latest commits: there at first copy+paste error in the "Add breakpoint function": print says "trying to remove" instead of "trying to insert". But that just a minor copy+paste error.

Next, I tried on x5000 firstly, that what we have on the serial:

<amigaos_init>
</
amigaos_init>
<
_initialize_amigaos_nat>
<
init_amigaos_ops>
</
init_amigaos_ops>
</
_initialize_amigaos_nat>
<
amigaos_can_run>
</
amigaos_can_run>
<
amigaos_can_run>
</
amigaos_can_run>
<
amigaos_create_inferior>
Shell ProcessCreating inferior processexec_file = /Work/aa/testargs = , env 0x617C27C0from_tty 1
<AllocateDebugInfo>
</
AllocateDebugInfo>
<
Ux2DOS>
</
Ux2DOS>
Shell ProcessGetting elf handle for seglist 0x188692F5
Shell Process
Process created0x66EDCDA0
Shell Process
Task0x66EDCDA0
Shell Process
Suspending Task
Shell Process
Adding debug hook from 0x66EDCDA0
Shell Process
Added debug hook for 0x66EDCDA0
Shell Process
amigaos target_pushed_count 0
Shell Process
pushing amigaos target
Shell Process
add_thread 1637021968 inf 0x617C2738
</amigaos_create_inferior>
<
amigaos_terminal_ours>
Shell Processterminal_ours is a STUB
</amigaos_terminal_ours>
<
amigaos_fetch_registers>
Shell Processinferior_ptid=0x6192F868
Shell Process
regno 64 (pc)
Shell Processcontext 0x6194CFC8sp 0pc 0lr 0
</amigaos_fetch_registers>
<
amigaos_has_execution>
</
amigaos_has_execution>
<
amigaos_has_registers>
</
amigaos_has_registers>
<
amigaos_has_stack>
</
amigaos_has_stack>
<
amigaos_has_memory>
</
amigaos_has_memory>
<
amigaos_has_registers>
</
amigaos_has_registers>
<
amigaos_has_stack>
</
amigaos_has_stack>
<
amigaos_has_memory>
</
amigaos_has_memory>
<
amigaos_has_registers>
</
amigaos_has_registers>
<
amigaos_has_stack>
</
amigaos_has_stack>
<
amigaos_has_memory>
</
amigaos_has_memory>
<
amigaos_has_registers>
</
amigaos_has_registers>
<
amigaos_has_stack>
</
amigaos_has_stack>
<
amigaos_has_memory>
</
amigaos_has_memory>
<
amigaos_has_registers>
</
amigaos_has_registers>
<
amigaos_has_stack>
</
amigaos_has_stack>
<
amigaos_has_memory>
</
amigaos_has_memory>
Shell ProcessTrying to insert breakpoint at 0x010004D4
<DoBreakpoint>
</
DoBreakpoint>
</
amigaos_memory_insert_breakpoint>
<
amigaos_has_registers>
</
amigaos_has_registers>
<
amigaos_has_stack>
</
amigaos_has_stack>
<
amigaos_has_memory>
</
amigaos_has_memory>
<
amigaos_can_run>
</
amigaos_can_run>
<
amigaos_resume>
Shell Processamigaos_resumerestarting 0x66EDCDA0
</amigaos_resume>
<
amigaos_debug_callback>
/
Work/aa/testamigaos_debug_callback task_p 0x66EDCDA0 (process=0x66EDCDA0)
/
Work/aa/testReceived DBHMT_OPENLIB (process=0x66EDCDA0)
/
Work/aa/testamigaos_debug_callback returning 0
</amigaos_debug_callback>
<
amigaos_debug_callback>
/
Work/aa/testamigaos_debug_callback task_p 0x66EDCDA0 (process=0x66EDCDA0)
/
Work/aa/testReceived DBHMT_OPENLIB (process=0x66EDCDA0)
/
Work/aa/testamigaos_debug_callback returning 0
</amigaos_debug_callback>
<
amigaos_can_run>
<
amigaos_debug_callback>
/
Work/aa/testamigaos_debug_callback task_p 0x66EDCDA0 (process=0x66EDCDA0)
</
amigaos_can_run>
/
Work/aa/testReceived DBHMT_CLOSELIB (process=0x66EDCDA0)
/
Work/aa/testamigaos_debug_callback returning 0
</amigaos_debug_callback>
<
amigaos_debug_callback>
/
Work/aa/testamigaos_debug_callback task_p 0x66EDCDA0 (process=0x66EDCDA0)
/
Work/aa/testReceived DBHMT_CLOSELIB (process=0x66EDCDA0)
/
Work/aa/testamigaos_debug_callback returning 0
</amigaos_debug_callback>
<
amigaos_debug_callback>
reaper.taskamigaos_debug_callback task_p 0x66EDCDA0 (process=0x66EDCDA0)
reaper.taskRecieved DBHMT_REMTASK (process=0x66EDCDA0)
reaper.taskamigaos_debug_callback returning 0
</amigaos_debug_callback>
<
amigaos_wait>
Shell Processwait ptid 0x66EDCDA0 (FFFFFFFF), status 0x6192F878kind 0
<is_process_alive>
</
is_process_alive>
Shell ProcessTarget has exited
</amigaos_wait>
<
amigaos_terminal_ours>
Shell Processterminal_ours is a STUB
</amigaos_terminal_ours>
<
amigaos_kill_inferior>
<
is_process_alive>
</
is_process_alive>
Shell ProcessNot Removing debug hook from IDebug 0x6FF910000x66EDCDA0 as process isn't alive
Shell Process: Killing 0x66EDCDA0
<FreeDebugInfo>
<is_process_alive>
</is_process_alive>
</FreeDebugInfo>
Shell Process: unpush target
</amigaos_kill_inferior>



And that what we have in the shell:

3/0.Work:aagdb_751_commit_43 -q test
_initialize_amigaos_nat 
[New inferior 0]
Reading symbols from /Work/aa/test...done.
(
gdb) break 1
break 1
target_memory_map 
()
target_get_section_table ()
exec:target_xfer_partial (2, (null), 0x6192f0380x00x10004d44) = 4bytes 3d 20 01 00
target_get_section_table 
()
exec:target_xfer_partial (2, (null), 0x6192f1080x00x10004d44) = 4bytes 3d 20 01 00
target_get_section_table 
()
exec:target_xfer_partial (2, (null), 0x6192f4580x00x10004d44) = 4bytes 3d 20 01 00
target_get_section_table 
()
exec:target_xfer_partial (2, (null), 0x6192f6d00x00x10004d44) = 4bytes =
 
3d 20 01 00
Breakpoint 1 at 0x10004d4
file test.cline 1.
(gdbr
r
t
PowerPC PPCBug monitor on port 0
 t
PowerPC PPCBug monitor on port 1
 t
DINK32 monitor
 t
Debug an Amiga process
 amigaos_can_run returning 1
t
Remote serial target in gdb-specific protocol
 t
Extended remote serial target in gdb-specific protocol
 t
Local trace dump file
 t
Local core dump file
 t
Local exec file
 t
Process record and replay target
 t
Process record and replay target
 Starting program
: /Work/aa/test 
t
PowerPC PPCBug monitor on port 0
 t
PowerPC PPCBug monitor on port 1
 t
DINK32 monitor
 t
Debug an Amiga process
 amigaos_can_run returning 1
t
Remote serial target in gdb-specific protocol
 t
Extended remote serial target in gdb-specific protocol
 t
Local trace dump file
 t
Local core dump file
 t
Local exec file
 t
Process record and replay target
 t
Process record and replay target
 
[New process 1726860704]
target_create_inferior (/Work/aa/test, , xxx1)
target_terminal_ours ()
target_get_section_table ()
subtask:target_xfer_partial (10target.xml0x64e78fd80x00x04095) = -1
target_thread_architecture 
(process 1726860704) = 0x617b8f30 [powerpc:common]
ptid_equal (null_ptidptid (17268607040,0)
pid 1726860704 for ptid (17268607040,0)
get_thread_arch_regcache (process 1726860704) = 0x617c26c8
ptid_equal 
(null_ptidptid (17268607040,0)
pid 1726860704 for ptid (17268607040,0)
get_thread_arch_regcache (process 1726860704) = 0x617c26c8
target_fetch_registers 
(pc) = 00000000 0x0 0
target_get_section_table 
()
subtask:target_xfer_partial (11, (null), 0x64e794300x00x04095) = -1
target_memory_map 
()
target_get_section_table ()
subtask:target_xfer_partial (2, (null), 0x6192f2f80x00x10004d44) = 4bytes 3d 20 01 00
ptid_equal 
(null_ptidptid (17268607040,0)
pid 1726860704 for ptid (17268607040,0)
get_thread_arch_regcache (process 1726860704) = 0x617c26c8
ptid_equal 
(null_ptidptid (17268607040,0)
pid 1726860704 for ptid (17268607040,0)
get_thread_arch_regcache (process 1726860704) = 0x617c26c8
target_insert_breakpoint 
(0x010004d4xxx) = 0
ptid_equal 
(null_ptidptid (17268607040,0)
pid 1726860704 for ptid (17268607040,0)
get_thread_arch_regcache (process 1726860704) = 0x617c26c8
ptid_equal 
(null_ptidptid (17268607040,0)
pid 1726860704 for ptid (17268607040,0)
get_thread_arch_regcache (process 1726860704) = 0x617c26c8
t
PowerPC PPCBug monitor on port 0
 t
PowerPC PPCBug monitor on port 1
 t
DINK32 monitor
 t
Debug an Amiga process
 amigaos_can_run returning 1
t
Remote serial target in gdb-specific protocol
 t
Extended remote serial target in gdb-specific protocol
 t
Local trace dump file
 t
Local core dump file
 t
Local exec file
 t
Process record and replay target
 t
Process record and replay target
target_terminal_inferior 
()
target_resume (-1, continue, 0)
 
tPowerPC PPCBug monitor on port 0
 t
PowerPC PPCBug monitor on port 1
 t
DINK32 monitor
 t
Debug an Amiga process
asdf
 amigaos_can_run returning 1
t
Remote serial target in gdb-specific protocol
 t
Extended remote serial target in gdb-specific protocol
 t
Local trace dump file
 t
Local core dump file
 t
Local exec file
 t
Process record and replay target
 t
Process record and replay target
target_wait 
(-1status) = 1726860704,   status->kind exitedstatus 0
target_terminal_ours 
()
 [
Inferior 1 (process 1726860704exited normally]
target_close (0)
target_mourn_inferior ()
target_terminal_ours ()
(
gdb)



At this point "break" didn't break. I.e. all execution continue till the end, without stopping on my breakpoint.


Then I tried also on pegasos2 just in case and the same result. So it's not an x5k specific issue for now: on both platforms breakpoints sets, but the process didn't stop, so we can checking registers, stack, doing "steps", etc.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: GDB
Quite a regular
Joined:
2007/2/6 13:57
From Donostia (SPAIN)
Posts: 632
@kas1e

Will try your build ASAP.
Maybe I missed some option when building GDB myself.

THX

   Report Go to top

Re: GDB
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 7022
@Javier
You just need to copy+paste things from readme, i.e.:

cd gdb-7.5.1
mkdir gdb
-build
cd gdb
-build
../configure --host=ppc-amigaos --target=ppc-amigaos --build=x86_64 --disable-nls --disable-werror --disable-sim LDFLAGS="-lunix"
make -j4


But for now, testing will make no big sense anyway, as breakpoints seem not works at the moment. I.e. they seem installed, but the process didn't pause as I can see from the log, and instead continue till the end.


@billifish

Btw, do you think we need "debug interrupts to work" there in GDB at this point? I mean, to have the ability to use just software breakpoints (which we tried to do now)? I think no? I just fear that debug-interrupts don't work on x5000 at all currently.


Edited by kas1e on 2021/3/21 14:26:22
_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: GDB
Quite a regular
Joined:
2007/2/6 13:57
From Donostia (SPAIN)
Posts: 632
@kas1e

yep, that's what I'm doing to build.

Build this one, hope is the one you say:

commit f6523629f1902115ee0a0700c14498ccf67b7187 (HEAD)
Author: a1200 <amiga1200@amiga.com>
Date: Thu Mar 4 20:46:42 2021 +0300

gdb/exec.c : added amigaos4 file attach hook the same as were done in 6.3a before. Making also exec_seglist in gdb/amigaos-nat.c/amigaos_create_inferior be not NULL, so we can go futher


Just wanted a not crash/freeze version of GDB.

   Report Go to top

Re: GDB
Just popping in
Joined:
2011/7/20 20:01
From In the sticks
Posts: 172
@kas1e

Quote:

But for now, testing will make no big sense anyway, as breakpoints seem not works at the moment. I.e. they seem installed, but the process didn't pause as I can see from the log, and instead continue till the end.


Ack, was worth a try but I couldn't test the code to check so hopefully it's a simple fix to get it working. I should have a new hard drive in the next day or two so I'll then be able to get my amiga working again as it has had to donate its hard drive to the computer I use for work.


Quote:

Btw, do you think we need "debug interrupts to work" there in GDB at this point? I mean, to have the ability to use just software breakpoints (which we tried to do now)? I think no? I just fear that debug-interrupts don't work on x5000 at all currently.


They're definitely something I want to get working, basically if a program crashes when running under GDB it will be the debug interrupt that will be called and stop the program at that point so you can inspect what is wrong. It requires the breakpoint code to be working first so that's the priority

As for the X5000, I hope it will work but I'll be relying on you for testing as I've just got an X1000

@jabirulo

The error message that you were getting was in the bfd part of the code and unless I've done something really stupid, which is always possible , the last few commits shouldn't have affected that as I haven't been touching that part of the code.

If you run sashimi, it should produce a debug output which will hopefully give more of an insight.

The only thing that I can think of that you're doing differently is that you're building it on Cygwin and I'm on Linux, I'm not sure what Roman is using. This might what the problem is as the code that builds gdb uses sed sometimes to get certain functions to add to gdb's automatically-generated code and this normally is at the start of a line, so it might be a line terminator issue?


   Report Go to top

Re: GDB
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 7022
@billyfish
Quote:

The error message that you were getting was in the bfd part of the code and unless I've done something really stupid, which is always possible, the last few commits shouldn't have affected that as I haven't been touching that part of the code.


No no, I tested your latest commit today: all builds and works as expected (i.e. binary loads, etc and breakpoints do not work as I wrote). But it definitely runs and loads up binaries as before.


On my side I use Cygwin.

My bet that Javier may try to build it differently (i.e. configure part), and that can be the reason for failure.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: GDB
Just popping in
Joined:
2011/7/20 20:01
From In the sticks
Posts: 172
@kas1e

Quote:

No no, I tested your latest commit today: all builds and works as expected (i.e. binary loads, etc and breakpoints do not work as I wrote). But it definitely runs and loads up binaries as before.


phew!

Quote:

On my side I use Cygwin.

My bet that Javier may try to build it differently (i.e. configure part), and that can be the reason for failure.


That would definitely be the best scenario

   Report Go to top

Re: GDB
Quite a regular
Joined:
2007/2/6 13:57
From Donostia (SPAIN)
Posts: 632
@kas1e

THX tested your GDB and works fine

Will see what I did wrong on my build.

#SDK:C/gdb helloworld
_initialize_amigaos_nat
[New inferior 0]
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "ppc-amigaos".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /Devel/SDK/ejemplos/helloworld...done.
(gdb) list
list
target_memory_map ()
target_get_section_table ()
exec:target_xfer_partial (2, (null), 0x58eb4488, 0x0, 0x10004d4, 4) = 4, bytes = 3d 20 01 00
target_get_section_table ()
exec:target_xfer_partial (2, (null), 0x58eb4558, 0x0, 0x10004d4, 4) = 4, bytes = 3d 20 01 00
1 ;/*
2 ppc-amigaos-gcc helloworld.c -o helloworld -gstabs -Wall
3 quit
4 */
5
6 #include <stdio.h>
7
8 int main(void)
9 {
10 printf("asd\n");
(gdb)



Edited by jabirulo on 2021/3/22 13:15:26
Edited by jabirulo on 2021/3/22 13:16:43
   Report Go to top


« 1 ... 4 5 6 (7) 8 »



[Advanced Search]



Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project