debugging with gdb in HP-PARISC2.0(64 bit)

[Thiagu_1]

am running my application in HP-PARISC 2.0(64 bit).
I compiled & linked my application with +objdebug option.

when I am trying to debug my application I am getting the following error.

[New process 24300]
Detaching after fork from process 24300
[New process 24477]
Detaching after fork from process 24477
[New process 24480]
Detaching after fork from process 24480
[New process 24482]
Detaching after fork from process 24482
[New process 24867]
Detaching after fork from process 24867
[New process 24922]
Detaching after fork from process 24922
[New process 24929]
Detaching after fork from process 24929
[New process 24934]
Detaching after fork from process 24934
[New process 24940]
Detaching after fork from process 24940
[New process 24946]
Detaching after fork from process 24946
[New process 24952]
Detaching after fork from process 24952
[New process 24991]
Detaching after fork from process 24991
[New process 24994]
Detaching after fork from process 24994
[New process 24999]
Detaching after fork from process 24999
[New process 25001]
Detaching after fork from process 25001
[New process 25004]
Detaching after fork from process 25004
[New process 25008]
Detaching after fork from process 25008
[New process 25037]
Detaching after fork from process 25037
[New process 25048]
Detaching after fork from process 25048
[New process 25053]
Detaching after fork from process 25053
[New process 25068]
Detaching after fork from process 25068
[New process 25074]
Detaching after fork from process 25074
---Type to continue, or q to quit---
[New process 25211]
Detaching after fork from process 25211
[New process 26569]
Detaching after fork from process 26569

When I Placed break point in some files which are linked with that exe I am getting the following " Which has no line number information "

[Switching to thread 4 (system thread 8720590)]

Breakpoint 1, 0x4000000001684fb0 in
writer::writeImages+0x58 ()
(gdb) next
Single stepping until exit from function writeImages__6LclWtrFPCcR11RWTPtrSlistXT16remoteImageEntryTQ2_3std9alloca
torXTP16remoteImageEntry__RC19RWTPtrOrderedVectorXT15remoteHostEntryTQ2_
3std9allocatorXTP15remoteHostEntry__,
which has no line number information.
0x4000000001684fc0 in writer::writeImages+0x68 ()

I am attaching tusc output for gdb and My application.

What could be the reason for this?

[Dennis Handly]

What version of gdb are you using?

Have you make the object file available to gdb with objectdir command? Especially if you moved it.

What happens if you don't compile that object with +objdebug?

[Dennis Handly]

Your tusc output for your application probably isn't interesting, unless you can point to something.

Looking at the opens in gdb, is your writeImages in libdsshare.a, AttrString.cpp or /InspectedWafer.cpp??

Perhaps I should ask if writer::writeImages was compiled with -g?

[Thiagu_1]

gdb Version:
$ gdb -v
HP gdb 5.2 for PA-RISC 2.0 (wide), HP-UX 11.00
and target hppa2.0w-hp-hpux11.00.

Compiler version:
$ aCC -V
aCC: HP ANSI C++ B3910B A.03.65

Object file is available in that scope only.

writeimages was compiled with +objdebug option and is in libklawtr.a

libklawtr.a is linked with My exe. I am able to place break point in libdsimpl.a which is also linked to that exe. After libdsimpl.a
I will reach libklawtr.a but I am not able to place break point there.

when I compiled libklawtr.a with -g option I am able to place break point in writeimages. My exe is linked with other ".a"s by +objdebug option.

[Dennis Handly]

>when I compiled libklawtr.a with -g option I am able to place break point

+objdebug is a modifier to -g, if you don't have -g, you don't get debug info. (Though it does seem to work differently with +DD32. )-: