Debugger wont trace source.

What the!?
The Flex environment is great. Debugs well. I especially like
the "Expressions" watcher. However, if I place my script code into
files then the debugger ignores every break point in those files.
For example, if I have a component and use the command:
<mx:Script source="theScriptsAreHere.as"/> then run
the app it works fine. But if I want to trace it then too bad. The
debugger simply refuses to enter the "theScriptsAreHere.as" script
file.
Perhaps there is a switch or something I have left out of
somewhere. Does anyone else experience this problem? Any comments
appreciated.
Cheers.

Thanks for your reply Tracy. It's good to know that I'm not
the only one :-)
I have searched the archives and found one other person
(AlainF) who posted a month ago. Unfortunately no response was sent
to them.

Similar Messages

XCode wont find source code during debug

My XCode project (an exernal target initially generated using GNU autotools, and imported into XCode) won't find the source code during debug.
I'm sure this is a project setup issue, but i can't seem to figure out which setting i need to change.
Any help is appreciated.
Thanks

Hi,
make sure Debug symbols are generated! If you for example choose to debug while the project is set to "Release" mode (Project->Set Active Build Configuration), you will not get your code displayed and instead have to use the asm output of the debugger.
If set to "Debug", XCode switches all necessary gcc... parameters for debugging.
Volker

Random Account Lockout (How to trace source?)

In Windows 2003 server native domain environment: XP Pro machines have no issues, but all ~10 PCs that have Win7 Pro (in different offices) have their domain accounts locked out randomly throughout the day. Workstations have no passwords listed in credentials
management.
Suspect it is something on the workstations that is sending incorrect logon and triggering the invalid password lockout limit on domain policy. Found MSFT tools to trace in XP, but nothing for Win7. Does anyone know how to use Procmon or similiar tool to
trace such source on the workstations? Thank you.
(Procmon.exe from systernals)

Hi,
The user account has been automatically locked because too many invalid logon attempts or password change attempts have been requested.
We can run the LockoutStatus.exe on domain controller to identify and investigate the account lockout issue.
Troubleshooting tools:
By using this tool, we can gather and displays information about the specified user account including the domain admin's account
from all the domain controllers in the domain. In addition, the tool displays the user's badPwdCount value on each domain controller. The domain controllers that have a badPwdCount value that reflects the bad password threshold setting for the domain are the
domain controllers that are involved in the lockout. These domain controllers always include the PDC emulator operations master.
You may download the tool from the link
Download Account Lockout Status (LockoutStatus.exe)
http://www.microsoft.com/downloads/details.aspx?familyid=D1A5ED1D-CD55-4829-A189-99515B0E90F7&displaylang=en
Once we confirm the problematic computer, we can perform further research to locate the root cause. Actually, there are many possible
causes for bad password, such as cached password, schedule task, mapped drives, services, etc. Please remove the previous password cache which may be used by some applications and therefore cause the account lockout problem.
Troubleshooting steps:
1. Click Start, click Run, type "control userpasswords2" (without the quotation marks), and then click OK.
2. Click the Advanced tab.
3. Click the "Manage Password" button.
4. Check to see if these domain account's passwords are cached. If so, remove them.
5. Check if the problem has been resolved now.
If there is any application or service is running as the problematic user account, please disable it and then check whether the problem
occurs.
For your convenience, I'd like to list the common troubleshooting steps and resolutions for account lockouts as the following:
Common Causes for Account Lockouts
To avoid false lockouts, please check each computer on which a lockout occurred for the following behaviors:
Programs:
Many programs cache credentials or keep active threads that retain the credentials after a user changes their password.
Service accounts:
Service account passwords are cached by the service control manager on member computers that use the account as well as domain controllers.
If you reset the password for a service account and you do not reset the password in the service control manager, account lockouts for the service account occur. This is because the computers that use this account typically retry logon authentication by using
the previous password. To determine whether this is occurring, look for a pattern in the Netlogon log files and in the event log files on member computers. You can then configure the service control manager to use the new password and avoid future account
lockouts.
Bad Password Threshold is set too low:
This is one of the most common misconfiguration issues. Many companies set the Bad Password Threshold registry value to a value lower
than the default value of 10. If you set this value too low, false lockouts occur when programs automatically retry passwords that are not valid. Microsoft recommends that you leave this value at its default value of 10. For more information, see "Choosing
Account Lockout Settings for Your Deployment" in this document.
User logging on to multiple computers:
A user may log onto multiple computers at one time. Programs that are running on those computers may access network resources with
the user credentials of that user who is currently logged on. If the user changes their password on one of the computers, programs that are running on the other computers may continue to use the original password. Because those programs authenticate when they
request access to network resources, the old password continues to be used and the users account becomes locked out. To ensure that this behavior does not occur, users should log off of all computers, change the password from a single location, and then log
off and back on.
Stored user names and passwords retain redundant credentials:
If any of the saved credentials are the same as the logon credential, you should delete those credentials. The credentials are redundant
because Windows tries the logon credentials when explicit credentials are not found. To delete logon credentials, use the Stored User Names and Passwords tool. For more information about Stored User Names and Passwords, see online help in Windows XP and the
Windows Server 2003 family.
Scheduled tasks:
Scheduled processes may be configured to using credentials that have expired.
Persistent drive mappings:
Persistent drives may have been established with credentials that subsequently expired. If the user types explicit credentials when
they try to connect to a share, the credential is not persistent unless it is explicitly saved by Stored User Names and Passwords. Every time that the user logs off the network, logs on to the network, or restarts the computer, the authentication attempt fails
when Windows attempts to restore the connection because there are no stored credentials. To avoid this behavior, configure net use so that is does not make persistent connections. To do this, at a command prompt, please type net use /persistent:no. Alternately,
to ensure current credentials are used for persistent drives, disconnect and reconnect the persistent drive.
Active Directory replication:
User properties must replicate between domain controllers to ensure that account lockout information is processed properly. You should
verify that proper Active Directory replication is occurring.
Disconnected Terminal Server sessions:
Disconnected Terminal Server sessions may be running a process that accesses network resources with outdated authentication information.
A disconnected session can have the same effect as a user with multiple interactive logons and cause account lockout by using the outdated credentials. The only difference between a disconnected session and a user who is logged onto multiple computers is that
the source of the lockout comes from a single computer that is running Terminal Services.
Service accounts:
By default, most computer services are configured to start in the security context of the Local System account. However, you can
manually configure a service to use a specific user account and password. If you configure a service to start with a specific user account and that accounts password is changed, the service logon property must be updated with the new password or that service
may lock out the account.
Internet Information Services:
By default, IIS uses a token-caching mechanism that locally caches user account authentication information. If lockouts are limited to users who try to gain access
to Exchange mailboxes through Outlook Web Access and IIS, you can resolve the lockout by resetting the IIS token cache. For more information, see "Mailbox Access via OWA Depends on IIS Token Cache" in the
Microsoft Knowledge Base.
MSN Messenger and Microsoft Outlook:
If a user changes their domain password through Microsoft Outlook and the computer is running MSN Messenger, the client may become locked out. To resolve this behavior,
see "MSN Messenger May Cause Domain Account Lockout After a Password Change" in the
Microsoft Knowledge Base.
For more information, please refer to the following link:
Troubleshooting Account Lockout
http://technet.microsoft.com/en-us/library/cc773155.aspx
Account Passwords and Policies in Windows Server 2003
http://technet.microsoft.com/en-us/library/cc783860.aspx
Hope this helps!
Novak

Bochs-with-debugger wont compile

Hello
Im trying to compile bochs with the option that includes wxgtk but I am not able to compile it.
It failes with an error wx.lo not found.
I have installed lib32-wxgtk and wxgtk
What could be the problem? I didnt find anything relevant on Google, or anywhere else.

# Mantainer: WinterXMQ <WinterXMQ at gmail dot com>
# Contributor: WinterXMQ <WinterXMQ at gmail dot com>
pkgname=bochs-with-debugger
_pkgrealname=bochs
pkgver=2.6.2
pkgrel=3
pkgdesc="A portable x86 PC emulation software package with builtin debugger"
arch=('i686' 'x86_64')
license=('LGPL')
url="http://bochs.sourceforge.net/"
source=(http://downloads.sourceforge.net/project/${_pkgrealname}/${_pkgrealname}/${pkgver}/${_pkgrealname}-${pkgver}.tar.gz)
sha512sums=('b35cf940520d2489657a1724f399553f7a52428fd4a84b1c38452723cc47bfbc242853489701c1aa577903045ce3dae4ca475c8934953b66bcc247d50835c7d3')
depends=('gcc-libs' 'libxrandr' 'gtk2')
conflicts=('bochs')
build() {
cd "${srcdir}/${_pkgrealname}-${pkgver}"
## build Debug Bochs
./configure \
--enable-smp \
--with-x11 \
--with-sdl \
--enable-smp \
--enable-3dnow \
--enable-x86-64 \
--enable-avx \
--enable-debugger \
--enable-x86-debugger \
--enable-long-phy-address \
--enable-plugins \
--enable-all-optimizations \
--enable-disasm \
--enable-pcidev \
--enable-usb \
--disable-docbook \
--enable-cpp \
--prefix=/usr
## add libaray pthread(is not Linux default libaray), because of missing DSO
sed -i 's/^LIBS = /LIBS = -lpthread/g' Makefile
make
package() {
cd "${srcdir}/${_pkgrealname}-${pkgver}"
make DESTDIR="${pkgdir}" install
install -D -m 644 .bochsrc "${pkgdir}/etc/bochsrc-sample.txt"
This one, however, i added the --with-wx compiler option

Stupidly easy - trace source to debug output inunit test...

I'm convinced that this is stupidly easy, but I cant figure it out...
I have a class with "TraceSource "classname" and in debugging it work fine, I see the output in the "output" window, however when running unittests I only see "debug.Write" output...
What am I missing... do I need to add a listener route or something?!
- sure I'm noJedi but that's no reason to stop trying to make stuff levitate! -
to clarify...this UnitTest:
[TestMethod()]
public void TestLogging()
System.Diagnostics.Debug.WriteLine("this is a debug writeline");
System.Diagnostics.Trace.WriteLine("this is a Trace writeline");
var ts = new System.Diagnostics.TraceSource("classname");
ts.TraceInformation("this is a ts.TraceInformation");
throw new AssertInconclusiveException();
outputs this:
Test Name: TestLogging
Test Outcome: Skipped
Result Message: Exception of type 'Microsoft.VisualStudio.TestTools.UnitTesting.AssertInconclusiveException' was thrown.
Result StandardOutput:
Debug Trace:
this is a debug writeline
this is a Trace writeline
Now... for SOME reason, THIS is NOT outputing to the DebugOutput either... when I step through the TEST...
however stepping through code NOT in unit test does put stuff in the debug output window...
What am I missing... why is the TraceSource not outputting... I can see in step through that the DefaultTraceListener is there (its the only listener) and I was under the impression that it directed output to the DebugOut output stream... is this not what
I think it is...?!

Hi Jack,
I think you are correct in that my expectations were wrong.
1) stepping through "SwitchLevel" is "Off", in the unit test, which is problematic.
turning it on (to All) starts logging, but ONLY when I manually add a CONSOLETraceListener (and set the route to debug error stream to true)
2) the doco you've pointed me at was what I was reading, but I think I read/misread it differently than you...
I think its this that threw me:
•A DefaultTraceListener emits Write and WriteLine messages to the OutputDebugString and to the Debugger.Log method. In Visual Studio, this causes the debugging messages to appear in the Output window. Fail and failed Assert messages also emit to the OutputDebugString Windows API and the Debugger.Log method, and also cause a message box to be displayed. This behavior is the default behavior for Debug and Trace messages, because DefaultTraceListener is automatically included in every Listeners collection and is the only listener automatically included.
to my thinking this means that by default a "Default -> aka Debug (when DEBUGGGING)" is created for you always, and therefore in the ABSENCE of config stuff, this would be perfect for UNITTESTING - therefore TraceSource with nothing but a name
should effectively produce the same output as "Debug.WriteLine"...
that was my thinking, but it looks like even with 'SourceLevel.All" you still need to fiddle with it...
Thanks for your input, for now, I've resolved this by adding the above stuff so that my existing TraceSources are at least outputting stuff in my tests so I can see more of what is going on without having to change my "TraceSource" calls to "Debug"
calls everywhere.
- sure I'm noJedi but that's no reason to stop trying to make stuff levitate! -

Stateless Controller - Debugger wont start

Hi,
I am trying to debug a controller. Debugger just wont start when its declared as stateless. As soon as I declare it as stateful, debugger starts.
Can someone please tell me how to debug in a stateless scenerio?
Thanks

Hi Shalaxy,
Have you tried with external breakpoints?(i.e se80->BSP page->utilities->External breakpoints->activate/deactivate or CtrlShiftF11. )
Try with the below mentioned option,
goto SICF --> Service name ex:HCM_LEARNING --> press F8 -->place curson on HCM_LEARNING -->
goto Edit --> Debugging -->Activate debugging.
Let me know if you have any queries.
Regards
Bhaskar Arani

Debugger Wont Start

When I try to run the Mapping Debugger in the 10.1.0.2 client running against a Solaris 5.9 based 9.2.0.6 database, the debugger stops at "Configuring Sources and Targets" and just sits there. I have connected to the Target Schema which does exist and was created with the Runtime Repository Assistant. Is this due to a bug or does this step just take a long time?
Thanks,
TGF

Have you tried using a 9.2 client???

Debugger wont run

Hi,
I cant get the debugger to work in flashbuilder 4.6
The trace commands dont work as I get this error
I cant see the trace commands outputted anywhere
I downloaded the debugger
http://download.macromedia.com/pub/flashplayer/updaters/11/flashplayer_11_sa_debug.exe
C:\Windows\System32\Macrom
ed\Flash\NPSWF32_11_4_402_287.dll
Flash Builder cannot locate the required debugger version of Adobe Flash Player. You might need to install the debugger version of the Flash Player or reinstall Flash Builder.

Are you testing locally (not in a webpage)? You should update your players here:
C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\player\win\11.4
For a browser, what does the FlashInstall.log report? Here's my latest install:
Plugin:
=O====== M/11.4.402.287 2012-10-22+13-10-46.273 ========
0000 [I] 00000010 "C:\Users\user~1\AppData\Local\Temp\{EA92BEA3-8B7E-4BEE-973A-ABB67D5B2126}\InstallFlashPl ayer.exe" -install -skipARPEntry -iv 8 -au 4294967295
0001 [I] 00000020 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl
0002 [W] 00001037 SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player Plugin/ 2
0003 [W] 00001036 Software\Mozilla\MaintenanceService\extensions/Plugins 2
0004 [W] 00001036 Software\Opera Software/Last CommandLine 2
0005 [W] 00001036 Software\Opera Software/Last CommandLine 2
0006 [W] 00001036 Software\Opera Software/Plugin Path 2
0007 [W] 00001036 Software\Opera Software/Plugin Path 2
0008 [I] 00000014 C:\Windows\system32\Macromed\Flash\NPSWF64_11_4_402_287.dll
0009 [I] 00000015 C:\Windows\system32\Macromed\Flash\FlashUtil64_11_4_402_287_Plugin.exe
0010 [I] 00000019 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl
0011 [I] 00000012
ActiveX:
=O====== M/11.4.402.287 2012-10-22+13-13-21.272 ========
0000 [I] 00000010 "C:\Users\user~1\AppData\Local\Temp\{F86CA5EA-9399-4DFA-97BA-60B367039EED}\InstallFlashPl ayer.exe" -install -skipARPEntry -iv 8 -au 4294967295
0001 [I] 00000020 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl
0002 [W] 00001037 SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player ActiveX/ 2
0003 [I] 00000013 C:\Windows\system32\Macromed\Flash\Flash64_11_4_402_287.ocx
0004 [I] 00000015 C:\Windows\system32\Macromed\Flash\FlashUtil64_11_4_402_287_ActiveX.exe
0005 [I] 00000016 C:\Windows\system32\Macromed\Flash\FlashUtil64_11_4_402_287_ActiveX.dll
0006 [I] 00000019 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl
0007 [I] 00000012

Why does debugger not find source code when compiler output has been directed to the root directory, but the source is in a sub-directory, using Forte for JAVA community edition V3.0

I have configured Forte to put compiler output, i.e. my classes, in the root directory of the project. I now find that the debugger does not find the source code when it is in a sub-directory. However, if I temporarily copy a classes' source code to the root directory the debugger will display it.
To direct compiler output to the root directory I selected Project >Settings>Compiler types, then External Compiler ( which is the default compiler in my case ) and set Target to be the root project directory. This is the only directory it will allow.

This Forum is for Forte 4GL or UDS as its called today. I am not sure if anybody is going to be able to answer your question here. Sorry.
ka

[2514] Remote debugger asks for source file.

I've been testing the fixed remote debug facility in the new release.
It is now possible to connect to a remote session and start debugging, but as soon as I hit a breakpoint a dialog pops up saying that it is unable to find the source file for the package being debugged. It offers various options, including two 'Look for file in connection ....'
and browsing for the source file.
If I do a local debug first, this does not happen.

We have a bug logged for "unable to find the source". You need to accept the dialog and select the connection you want to do the debugging on. For the other issue, we have multiple databases, with connections for users with the same name in each and have not run into the issue described. Please can you provide more detail.
Sue

Stp loop, Not able to trace source

Hello,
I am new to cisco switches and learning about cisco switches now. we have a LAN with 6509 as core router and 2950s/3550s as access switches.
When I ran wireshark on my machine, I saw an stp loop repeating from a cisco device. I have noted down the MAC-address and tried in vain to find the same in our LAN. I am seeing packets like Address: "Spanning-tree-(for-bridges)_00" and "loop reply". I am not able to see any of the MAC addresses found in this loop conversation, on my LAN. I read that these loops are not good for the network. Where can I start to resolve this problem?
Thanks in advance for your advice.

There is likely no problem at all. ;-)
If you were really experiencing a loop, you would have other problems.
Best for you will be to start making a study of spanning tree (STP) and it's inner workings. Here is a good starting point:
http://www.cisco.com/en/US/tech/tk389/tk621/tsd_technology_support_protocol_home.html
Armed with this knowledge you can try to analyze the traffic that was observed by wireshark.
regards,
Leo

Trace source of rapidly growing tablespace

A tablespace which has about 24 datafiles of 1GB each is growing fairly rapidly and I would like to know if it is easy and quick to evaluate the cause.
I appreciate I could gather details of all tables in the tablespace and monitor their size over a period of time, but is there any other "immediate" way?
Thanks

Hi,
I have two suggestions for you..
1. try to partition the table if it is huge .. and
2. try to take sampling (statistics) when you do analysis to reduce the run time..
Thanks
--Raman

ABAP Debugging Trace

Hi,
is there a built-in tool in the ABAP debugger to trace the complete source code and copy in a text file, for further analysis?
I would like to compare the source code for similar processes, to find gaps, for instance why the first process works as expected and the second one doesnt. If I have two files with the complete source code, that was proceeded from the debugger, than I could seek the source code position, where the erroneos method or function group branches otherwise.
Thanks!
Regards,
Laura

laura2010 wrote:
Hi,
>
> is there a built-in tool in the ABAP debugger to trace the complete source code and copy in a text file, for further analysis?
>
> I would like to compare the source code for similar processes, to find gaps, for instance why the first process works as expected and the second one doesnt. If I have two files with the complete source code, that was proceeded from the debugger, than I could seek the source code position, where the erroneos method or function group branches otherwise.
>
> Thanks!
>
> Regards,
> Laura
You may start your analysis/comparision with the files generated by the SE30(Runtime Analysis), this would give you a good overview of deviations at a high level, if you are looking for deviations within the same modularazation unit you may find [this blog|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22536] helpful, however you have to be on Netweaver 7.0 Ehp2
to be able to use the features explained.
-Rajesh.

Write a debugger using JDI

Hi,
I am new to JDI and I want to create a debugger to listen to events like
ClassUnloadEvent .
I start the application that I want to debug with:
java -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=80000 <mailclass>
is this correct ?
I than get the VirtualMachinceManager by:
VirtualMachineManager vmManager = Bootrap.virtualMachineManager();
But than I am lost how to continue and connect to the other VM that I wan to debug.
Anyone has an idea?

I suggest you start by taking a look at the trace example, which (in J2SE 1.4.x or 5.x) will be found in $JAVA_HOME/demo/jpda/examples.jar.
After you unpack examples jar, look for com/sun/tools/example/trace/Trace.java.
After you understand the trace example, take a look at the sample jdb debugger. The source for that will be located under: com/sun/tools/example/debug/tty

Source not found exception in JSF processing

Hope this is not a newbie question, but I am stuck here.
I am using jdk 1.5_07 with tomcat 5.5 and using Exadel studio for eclipse as my ide.
I have created a jsf page with a simple drop down menu. The menu gets its data from a backing bean, which in turn calls a business object that queries the database to get the data for the drop down.
When I run the page, it fails because it says it returns a null list.
In the debugger, i have stepped through the code and backing bean (session based) does everything it is supposed to, including updating the property in the object ArrayList<SelectItem>. When the backing bean is initialized, the constructor calls a method that initializes this property properly.
As soon as the initializiation is done, however, I get an error message in the debugger that:
"The source attachment does not contain the source for the file NativeMethodAccessorImpl.class. You can change the source attachment by clicking "Change Attached Source below:". Click on this button brings up a window for me to select my src.zip, prepopulated with C:/Program Files/Java/jdk1.5.0_07/src.zip. The file exists, I have checked it.
If I continue in the debugger, it then does call the getter method for the property, but at that point in time, the object is empty for whatever reason (again, it was a sesson bean), so that it returns a null to the jsf page, which then blows up because it got a null value.
I have no idea what is happening here - the message would seem to indicate a problem with my JDK, but it works fine for the example apps and in tomcat.
Any thoughts would be appreciated.
Thanks,
Rich

Subsequent to my last message, I found that if I put the initializer method call in the getter, it works. Meaning, if I have the initializer method in the constructor for the class, when the getter is called on the object, the data is not initialized and returns null. When I check for null in the getter and put the initializing method in the getter, it works fine. This would appear to be something to do with the lifecycle of the request - I am using a session scoped managed bean. Is there some kind of round trip between the method constructor call and the getter method? I would not think so, as the getter is what is instantiating the class in the first place, but I am new to JSF so I am not sure what is happening.

Debugger wont trace source.

Similar Messages

Maybe you are looking for