243095 - a problem when setting a single component in XPCOM_BREAK_ON_LOAD

Status: RESOLVED DUPLICATE of bug 243429

(Core :: XPCOM, defect)

Description

[Boying Lu]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a) Gecko/20040507
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a) Gecko/20040507

If you want to break in some component (shared library) say libxpcom.so
if you using the following gdb command to set the environment XPCOM_BREAK_ON_LOAD:
  set env XPCOM_BREAK_ON_LOAD xpcom
and then "run" the program.

gdb will not break after loading the libxpcom.so as you expect.
which you should use: set env XPCOM_BREAK_ON_LOAD "xpcom:" instead
which is very unconevient for developer.
according to the document "http://www.mozilla.org/unix/debugging-faq.html"
we don't need to add a colon at the end if there is only one component we are
interesting.


Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Boying Lu]

Attachment: patch v0

Comment 2

[Boying Lu]

Comment on attachment 148038 [details] [diff] [review]
patch v0

Can you give r?

Comment 3

[Boying Lu]

Attachment: patch v1

The root cause is the implementation of nsCString::Find() has been changed.

Comment 4

[Boying Lu]

Comment on attachment 148039 [details] [diff] [review]
patch v1

Can you give r now?

Comment 5

[Boying Lu]

Comment on attachment 148039 [details] [diff] [review]
patch v1

Can you give r?

Thanks

Comment 6

[David Bradley]

Comment on attachment 148039 [details] [diff] [review]
patch v1

r=dbradley

Looks fine to me. Did Find use to treat -1 as the beginning?

Comment 7

[Boying Lu]

Comment on attachment 148039 [details] [diff] [review]
patch v1

Can you give sr?
Thanks

Comment 8

[Boying Lu]

No, Find() doesn't treat -1 as beginning

Comment 9

[Mike Shaver (:shaver emeritus)]

Comment on attachment 148039 [details] [diff] [review]
patch v1

sr=shaver

Comment 10

[Christian :Biesinger (don't email me, ping me on IRC)]

hmm. did bug 243429 fix this? especially in the light of comment 3

Comment 11

[Boying Lu]

Yes. I have verified that the patch of bug 243429 does solve the problem. So the
patch of this bug is not needed.

Comment 12

[Christian :Biesinger (don't email me, ping me on IRC)]

ok, in that case, marking as duplicate of bug 243429

*** This bug has been marked as a duplicate of 243429 ***