Problems with the dbx debugger

hey everyone,
i'm having a little problem with my dbx debugger.
the problem is that when i try to print a struct it print it as a struct from another type. i even tried casting the struct to its type and it still print it as the other type..
anyone had that problem and solved it? or maybe have any idea what could cause that problem?

thanks ahead,
Doron

Try gdb? I db very rarely, mostly for core stack trace, preferring lots of logging, debug flag controlled logging, error checking and truss/tusc/strace.

i didnt try gdb.. and i use log prints most of the time, but the problem i had seems really strange to me, and debugger would be halping me so i thougt maybe someone know what could cause it...
thanks anyway

Sorry I have no exact answer, just a few ways forward if no expert steps forth (Each reply moves you to the top of some lists!).

1. truss/tusc/strace can be turned on to various levels of detail, like in Solaris truss -u '*' shows all lib calls.
2. gdb is free of onerous licenses, and if it does not work, you can ask or there is source to unscrew mysteries or fix it yourself. I used to run a frequent cron on production to find all core, use file to identify them, locate the executable, use gdb to get a stack trace, mail that to me, and move the core to /tmp, compressed, for future reference or eventual purge (not necessarily in that order, but all good steps -- email has core original and final file names). It is amazing what your code can be up to, behind your back, on a server!

I'm afraid not unless this happen to be a well known bug.
Otherwise, that would be hard without knowing what OS you run, what dbx version you use, what programming language was used, what compiler was used to build the code, what code was referencing the structure, and even with all of that information, a reproducible case would likely be required to identify the source cause ...