- 1. Debugging the compiler with gdb (score: 1)
- Author: "Steven Tjiang" <tjiang@xxxxxxxxxxxxx>
- Date: Wed, 31 May 2000 10:54:25 -0700
- I am having problems debugging the be phase with I compiled the compiler with debugging on. This really bloats up the binaries but the real problem is that if you use gdb-4.18 on be, gdb grows to 460
- /archives/pro64-support/2000-05/msg00007.html (6,905 bytes)
- 2. Re: Debugging the compiler with gdb (score: 1)
- Author: Ding-Kai Chen <dkchen@xxxxxxxxxxxxx>
- Date: Wed, 31 May 2000 11:28:01 -0700
- I have used my gdb successfully a few times. Try ~dkchen/bin/gdb and see if it works better. Ding-Kai
- /archives/pro64-support/2000-05/msg00008.html (7,270 bytes)
- 3. Debugging the compiler with gdb (score: 1)
- Author: "Steven Tjiang" <tjiang@xxxxxxxxxxxxx>
- Date: Wed, 31 May 2000 10:54:25 -0700
- I am having problems debugging the be phase with gdb. I compiled the compiler with debugging on. This really bloats up the binaries but the real problem is that if you use gdb-4.18 on be, gdb grows t
- /archives/pro64-support/2000-05/msg00016.html (6,905 bytes)
- 4. Re: Debugging the compiler with gdb (score: 1)
- Author: Ding-Kai Chen <dkchen@xxxxxxxxxxxxx>
- Date: Wed, 31 May 2000 11:28:01 -0700
- I have used my gdb successfully a few times. Try ~dkchen/bin/gdb and see if it works better. Ding-Kai
- /archives/pro64-support/2000-05/msg00017.html (7,312 bytes)
This search system is powered by
Namazu