Using IDB (intel debugger)
Hi,
I know that this subject can be quite strange and that Sun could be hostile
but I would ask if it is possible to use the Intel fortran debugger with Sun
Studio 12.
I am asking this because dbx has never worked on both my computers (I have a P4 and a Core 2 duo).
Thanks,
Lello
[326 byte] By [
lello76a] at [2007-11-27 6:43:15]

# 1
Well, it definitely won't work from the IDE; IDE uses proprietory protocol for exchanging data and commands with dbx.
From the command line perspective, I see no reason why intel (or any other debugger for that matter) won't work with Sun Studio-generated binaries. Debugging information is DWARF and should be readable by other debuggers. There are Sun extensions, however, so I'm not sure that full functionality will be available (might be problems with C++ templates, for example).
By the way, which versions of Linux(es) do you have? Dbx was tested (and is supported) on Red Hat and SuSe, but is also known to work on several other distributions, like Ubuntu and Fedora, for example.
# 3
I know I can use idb from command line. I meant if it was possible to use it from the IDE. I have ubuntu 7.04 (and 6.10) and dbx has never worked with both versions.
If I put a break point it stops but after a few seconds I get a segmentation fault error. I don't know why, probably it's my code but I can debug it with idb...and if a wrong code can break the debugger, well, it can't be of any use.
Thanks for your reply,
Lello.
# 4
> Perhaps if you made an application called dbx that converted all
> commands/text to/from idb to mimic dbx.
No, this won't work. The protocol is more complex.
> If I put a break point it stops but after a few seconds I get a segmentation fault error.
It might be that the reason for crash is not Ubuntu, but smth else, so if you can help us to investigate the problem, we would be able to provide you with a fix.
Can you post dbx's stack trace at the moment of core dump here? From what I understand, you don't do anything before dbx crashes, so it looks like that updating locals/watches/whatever, which is happening in background, is causing this core dump.
As a workaround, you can try hiding one or more tabs with data and see if it helps.