attaching pathdb

[Barry Smith]

   Then it should "just work", what happens when you run
with -start_in_debugger noxterm,pathdb or
-start_in_debugger pathdb? Please send all output from
the error.

    Thanks

     Barry


On Tue, 28 Feb 2006, Harald Pfeiffer wrote:

> Hi Barry,
>
> the usage seems to be similar or even identical to gdb:
>
> Output of pathdb -help:
>>  usage: pathdb [option...] [program [core|pid]]
>
> The man page is online under http://www.pathscale.com/docs/pathdb.html,
> and there is also the full user guidem 
> http://www.pathscale.com/docs/PathDB_UserGuide.pdf (look at page 29).
>
> Harald
>
>
>
> Barry Smith wrote:
>>
>>   Harald,
>>
>>    We need to know the command line arguments for pathdb to attach
>> properly (each debugger is a little different, hence the hardwiring).
>> Please send us the pathdb man page and all the output when you
>> run it with -help and we'll make a tenative patch for you to try.
>>
>>    Barry
>> 
>> 
>> On Tue, 28 Feb 2006, Harald Pfeiffer wrote:
>> 
>>> Hello,
>>> 
>>> I'd like to use the pathscale debugger, pathdb, when debugging 
>>> petsc-codes. However, petsc seems to have hardcoded the list of debuggers:
>>> 
>>> -on_error_attach_debugger [gdb,dbx,xxgdb,ups,noxterm]
>>>      start the debugger in new xterm
>>> -start_in_debugger [gdb,dbx,xxgdb,ups,noxterm]
>>>      start all processes in the debugger
>>> 
>>> 
>>> How do I go about doing this?
>>> 
>>> Thanks,
>>> Harald
>>> 
>>> 
>
>